From an empty server to an ISiK-compliant healthcare backend — no FHIR team required, no regulatory deep-dive needed.
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.
Production Helm chart with HPA (2–10 pods), Pod Disruption Budget, Prometheus integration and rolling updates. AWS EKS, Azure AKS, GKE.
Fastest start for on-prem: one Compose file with all services, resource limits and health checks. Monitoring stack included.
Automated deployment on Ubuntu or RHEL. Docker installation, build, configuration and health checks — one command.
Each tenant gets isolated data via HAPI Partitioning. One gateway, unlimited facilities.
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.
ADT, ORU, ORM, SIU — the MLLP listener receives HL7v2 messages and automatically translates them to FHIR R4.
Your system has a REST interface? The REST adapter connects, fetches data and maps it to the 353 German FHIR profiles.
Even legacy systems without APIs can be connected — via file import, database views or the 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.
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.
Upload certificate, configure endpoint. The gateway speaks SOAP with the connector and exposes FHIR APIs.
OAuth2-based authentication against the Gematik Identity Provider — for ePA, E-Rezept and VZD access.
KIM transport (secure system-to-system messaging) and TIM transport (FHIR data exchange via TI-Messenger) — you choose your provider, we integrate the protocol.
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.
From this moment, your systems speak FHIR. ISiK-compliant. TI-connected. All on your server, under your control.
Level 4/5 — all mandatory profiles implemented. No manual profile work, no yearly rework.
Full HAPI FHIR R4 JPA Server — Search, CRUD, Bundles, Subscriptions, everything out of the box.
Admin portal with tenant management, API key management, onboarding wizard and real-time monitoring.
New ISiK level? New Gematik specification? We deliver the update. You deploy it. Done.
Not a prototype. Not an MVP. A production-ready healthcare backend.
Full HAPI FHIR JPA Server with Search, CRUD, Bundles, Transactions and Subscriptions.
ISiK, Gematik, KBV, MII, HL7 DE — every published German FHIR profile is registered and validated.
HSK, IDP, KIM transport, TIM transport, ePA, E-Rezept, VZD — the entire Telematikinfrastruktur through one gateway.
One gateway for unlimited facilities. Data strictly isolated via HAPI Partitioning.
Tenant management, onboarding wizard, API key management, dashboard and monitoring.
REST, HL7v2/MLLP, CSV, database — plus AI mapping assistant for proprietary formats.
Automated test suite including Gematik Reference Validator. Every update is validated.
Your server. Your data. Your control. On-premises, your own cloud or data center.