ISiK Interface: Connecting Your Software to Hospital Information Systems via FHIR

We connect your software to hospital information systems (HIS) via the standardized ISiK interface specified by gematik. From analyzing the available modules and development based on FHIR (Fast Healthcare Interoperability Resources) to rollout in the hospital. Certified to ISO 13485 and ISO 27001.

CONTACT US

Our services for the ISiK interface

We support you from the first feasibility check to operation in the hospital. This applies to any medical software that exchanges data with the HIS, for example clinical decision support systems, telemedicine and study platforms, or patient portals.

Analysis and feasibility

Analysis and feasibility

We clarify which data your software needs, which ISiK modules cover it and which stage the HIS of your target hospitals offer today.

Developing the FHIR connection

Developing the FHIR connection

We develop your software’s connection against the ISiK FHIR profiles, including search queries, error handling and logging.

Data mapping

Data mapping

We map your data model to FHIR resources such as Patient, Encounter, Appointment or DocumentReference and vice versa.

A solution for legacy systems

A solution for legacy systems

If an HIS does not yet support ISiK, we connect it via the older standard Health Level Seven Version 2 (HL7 v2) or a proprietary interface. An adapter layer keeps the later switch to ISiK simple.

Security and network

Security and network

We plan the connection to the hospital network, for example via a virtual private network (VPN), as well as authentication and encryption. Our information security management system is certified to ISO 27001.

Testing, rollout and maintenance

Testing, rollout and maintenance

We test with test data and test systems, support commissioning in every hospital and adapt your connection to new ISiK stages.

What is the gematik ISiK interface and how does it simplify your HIS integration?

ISiK stands for “Informationstechnische Systeme im Krankenhaus” (information technology systems in hospitals). Under this name, gematik specifies an open and standardized interface through which an HIS exchanges data with other systems, as mandated by Section 373 of the German Social Code Book V (SGB V). Technically, ISiK is a set of German profiles for FHIR. They define which data and search functions an HIS must provide, organized into modules such as Basis, Dokumentenaustausch (document exchange) and Terminplanung (appointment scheduling).

Approved hospitals must use systems that have successfully completed the prescribed conformity assessment procedure. Until now, a new hospital often meant a new interface. ISiK is meant to change that.

One interface instead of many

One interface instead of many

Instead of building a separate proprietary interface for every HIS vendor, you develop your connection once against the ISiK profiles. You can largely reuse this connection in every hospital whose HIS implements the same ISiK stage and the required modules.

Legally binding

Legally binding

ISiK stage 5 is set as binding in the Health IT Interoperability Governance Ordinance (GIGV). By 31 May 2027, it must be implemented in HIS. Your connection therefore builds on a standard set by ordinance.

A clear requirement in sales

A clear requirement in sales

You can give hospital customers a clear technical requirement, for example ISiK stage 5. What remains per hospital is mainly network access, approvals, configuration and testing.

CASE STUDY

INTEGRATE-ATMP: Telemedicine with HIS integration

For the INTEGRATE-ATMP project, we developed a telemedicine platform for gene therapies together with Heidelberg University Hospital. It connects the hospitals’ HIS, MARVIN-based registries, treating physicians, treatment centers and patients. The Innovation Fund of the Federal Joint Committee (G-BA) is funding the project with 13.6 million euros.

INTEGRATE-ATMP telemedicine platform as a web application for physicians and an app for patients

How we work

Connecting your software via the ISiK interface in three steps:

1. Assessment

1. Assessment

Together with you, the hospital and, if needed, the HIS vendor, we clarify which ISiK modules and stages are already available and how access to the hospital network works.

2. Design and development

2. Design and development

We design the architecture, define the data mapping and develop the connection. If your software is a medical device, we document the development according to IEC 62304.

3. Testing, rollout and operation

3. Testing, rollout and operation

We test the connection against test systems, support commissioning in the hospital and, on request, take over maintenance and further development.

What sets us apart

ISO 13485 certified

ISO 13485 certified

Our quality management system is certified to ISO 13485. This ensures compliant development of software as a medical device and meets the MDR requirements for quality management systems.

ISO 27001 certified

ISO 27001 certified

QuickBird Medical is certified to ISO 27001 for information security. We are experts in cybersecurity and data protection for health data.

Legal Manufacturer

Legal Manufacturer

If required, we take on the role of legal manufacturer for your medical device software and bear the legal responsibility for MDR compliance. This lets you focus on sales and marketing.

Frequently asked questions about the ISiK interface

ISiK vs. FHIR: What is the difference?

FHIR is an international standard by HL7 that describes health data as resources and exchanges them via web interfaces, among other things. ISiK builds on FHIR and defines for German hospitals which resources, data fields and search parameters an HIS must provide. Implementing ISiK therefore means implementing FHIR in a precisely defined form.

Which ISiK stage is currently binding?

According to gematik, the stage 3 modules have been mandatory since 1 July 2025, with the exception of the Security module. ISiK stage 5 has been set as binding in Annex 1 of the GIGV since 15 June 2026. By 31 May 2027, it must be implemented in HIS. Stage 6 was published on 1 July 2026. At the start of the project, we check which stage the HIS of your target hospitals actually offer.

Does every hospital already offer an ISiK interface?

No. The status varies from hospital to hospital. It depends on the HIS vendor, the version in use and whether the interface has been set up on site. That is why we talk to the hospital and, if needed, the HIS vendor right at the start.

What is the gematik ISiK confirmation?

Manufacturers of systems relevant for confirmation, such as an HIS, go through the gematik confirmation procedure. gematik publishes which systems are confirmed in its specialist portal. For your software, the confirmation of an HIS is a good indication that its interface implements the requirements of the confirmed stage and version.

What happens if a customer's HIS does not yet support ISiK?

Then we connect the HIS via HL7 v2 or a proprietary interface in the meantime. You can read more about this on our page on integration with HIS and practice management systems. An adapter layer separates this connection from the core logic of your software. This way you can switch to ISiK later without major rework.

Do you also support manufacturers who want to provide a FHIR interface themselves?

Yes. A FHIR server does not have to store its data internally in FHIR format. If required, we develop a FHIR layer on top of your existing database that exposes your data as FHIR resources.

Are you planning to connect your software to an HIS?

Our team supports you in planning and technically implementing your connection to the ISiK interface. Get in touch and arrange a no-obligation initial consultation. Let us find out together how we can support you with your project.