Questionnaire eEKP-FHIR UseCase 2026
Acknowledgement
The given structure of this track is mainly based on HL7 International's Connectathon Patient Track definition.
Short Description | Within the scope of the track, participants are enabled to implement and test both the authorization process and the Questionnaire-based interactions with a test environment. This includes, in particular, the structured capture and exchange of examination data related to birth using the defined FHIR-based artifacts from the eEKP-FHIR project. Furthermore, the end-to-end process and the required technical interactions for obtaining the necessary access prerequisites, i.e. obtaining and exchanging SAML-based Assertions for access tokens, and related authorization artifacts, can be tested and validated as part of the track. |
Long Description | The track provides a comprehensive testing scenario that mirrors the core integration principles of the eEKP-FHIR architecture. Participants are not only able to connect to a dedicated test environment, but can also walk through the complete security and access workflow required to access FHIR-based interaction endpoints for eEKP-FHIR. This includes simulating the identity and authorization chain starting with the acquisition of a valid Assertion (SAML), performing the necessary token exchange procedures, and obtaining OAuth2-based access tokens required to invoke the protected FHIR endpoints. Beyond the security layer, the track focuses on the functional interoperability aspects defined in the eEKP-FHIR specifications. Participants can retrieve and process the officially defined FHIR Questionnaire resources that model the structured documentation of examinations related to pregnancy and birth. These Questionnaires serve as canonical definitions for standardized data capture and are intended to be completed and submitted as FHIR QuestionnaireResponse resources. The scenario enables implementers to test both read and write use cases, ensuring correct implementation of resource structures as defined in eEKP-FHIR. |
Type | Experimental use of FHIR interactions, including authorization logic, for eEKP FHIR. |
Submitting Work Group/ | ELGA GmbH |
Track Lead(s) | |
Track Lead Email(s) | |
Related Tracks | https://hl7at.atlassian.net/wiki/x/AYCKOw (in case the basics are required) |
FHIR Version | All related Questionnaires and IHE-Profiles:
|
Specification(s) this track uses | In course of the eEKP-FHIR Track, we focus on 4 distinct Questionnaire definitions that are intendet to record the examinations related to pregnancy and birth. For reference, you can find the Questionnaire-definitions and a prebuild form rendering via |
Artifacts of focus |
|
Date / Time | Monday March 2nd, 09:00am-17:00pm CET |
Test Servers | A dedicated test server will be provided as part of the event. Access details and further information will be shared separately. |
Expected participants | In general this track is open for all participants. However, the track focusses on the following participants in particular:
|
Track Details | System Roles FHIR Client
eEKP FHIR Test System
Pre-Requisites (depending on use case) Example Instances Access to eEKP FHIR Test System will be provided in the course of the event. Level 1 Browser-based Questionnaire InteractionFor this level, participants are provided with a preconfigured browser client that already includes all required setup:
Participants interact solely through the UI and do not need to perform REST calls or manually work with JSON resources. Participants will learn:
This level intentionally hides technical complexity in order to focus on concepts:
This allows participants to concentrate on the functional aspects of questionnaires and their role in healthcare documentation. Success CriteriaParticipants successfully complete Level 1 when they can:
Step 1: Load a Questionnaire Step 2: Fill out answers and explore the dynamic form (enableWhen fields) in the UI and submit the QuestionnaireResposne Step 3: Load a previously submitted QuestionnaireResponse and edit it Level 2 API-Level Interactions (OAuth2 + FHIR)
Level 3 Service and API-Level Interactions (SAML + OAuth2 + FHIR)
|
Helpful Links | Security and Privacy considerations Do not submit personal data (in particular, social insurance numbers and the like). Development and Test clusters require authentication, but are not encrypted and hardened like a production instance would be - use only the provided pseudo certificates. |
