Informationstechnische Systeme in Krankenhäusern (ISiK) - 🇩🇪

Overview

Note

Firely Server v4 has been officially certified against ISiK Basis - Stufe 1. For more details, see our listing on gematik Fachportal - Bestätigungsübersicht Primärsysteme. The offical notice of compliance by gematik can be received upon request.

Firely Server is ready to comply with the mandatory and optional ISiK certification criteria without any additional configuration specified in ISiK - Supported Versions.

ISiK APIs

ISiK is categorized in different modules, each of which is versioned independently. Each ISiK module defines a set of minimal API interactions that an EHR needs to support. In most cases a read-only API combined with required and optional search parameters are defined. All required interactions are listed in the corresponding CapabilityStatement within each implementation guide.

ISiK Basis:

• ISiK Basis - “Stufe 1”

• ISiK Basis - “Stufe 2”

• ISiK Basis - “Stufe 3”

ISiK Vitalparameter und Körpermaße:

• ISiK - Vitalparameter und Körpermaße - “Stufe 2”

• ISiK - Vitalparameter und Körpermaße - “Stufe 3”

ISiK Medikation:

• ISiK - Medikation - “Stufe 2”

• ISiK - Medikation - “Stufe 3”

ISiK Dokumentenaustausch:

• ISiK - Dokumentenaustausch - “Stufe 2”

• ISiK - Dokumentenaustausch - “Stufe 3”

ISiK Terminplanung:

• ISiK - Terminplanung - “Stufe 2”

• ISiK - Terminplanung - “Stufe 3”

ISiK Sicherheit:

• ISiK - Sicherheit - “Stufe 2”

• ISiK - Sicherheit - “Stufe 3”

To implement an ISiK API it is necessary to:

1. Optionally, enable SMART on FHIR and point Firely Server to an authorization server managing the accounts of the patients - See Introduction Access control

2. Expose the Patient records with all their data elements defined by each implementation guide

3. Import the conformance resources defined by a module into the administration database of Firely Server to enable the validation against them - See Managing Conformance Resources

4. Enable the document handling plugin to support the submission of a “Bericht aus Subsystemen” - See Document endpoint

5. In case SMART on FHIR is enabled, configure the API clients to be allowed to be granted access (ready-only) to resources on behalf of the patient - See Configuration of API clients in Firely Auth

6. Note: Some modules define custom operations which - if not specified otherwise above - not supported out-of-the-box and need to be implement as a plugin in Firely Server - See Plugins