Table of Contents
In DEMIS users with various different backgrounds such as health care professionals, laboratory staff as well as citizens (in behalf of their company) can submit notifications. They use different authentication methods such as certificates, SMC-Bs as well as third party identity providers like BundID which provide varying levels of trust concerning the identification of the notifying person.
The Context Enrichment Service (CES) extracts information concerning the authentication and associated level of trust from the user's JWT and provides a FHIR resource to embed it into the notification by the calling services. That way RKI and health offices can better assess the credibility of the notifications received.
See ReleaseNotes for all information regarding the (newest) releases.
The application can be executed from a mvn command file or a Docker Image.
mvn clean verifyThe docker image can be built with the following command:
docker build -t context-enrichment-service:latest .
The image can alternatively also be built with maven:
mvn -e clean install -PdockerThe application can be started as Docker container with the following commands:
docker run --rm --name context-enrichment-service -p 8080:8080 context-enrichment-service:latestSubsequently we list the endpoints provided by the Context-Enrichment-Service.
| HTTP Method | Endpoint | Parameters | Body | Returns |
|---|---|---|---|---|
| POST | /enrichment | - header: Authorization (JWT TOKEN) - body: CompositionId |
The UUID of the Composition to refer to. | - FHIR-Provenance-Ressource |
If you want to see the security policy, please check our SECURITY.md.
If you want to contribute, please check our CONTRIBUTING.md.
Copyright 2024-2025 gematik GmbH
EUROPEAN UNION PUBLIC LICENCE v. 1.2
EUPL © the European Union 2007, 2016
See the LICENSE for the specific language governing permissions and limitations under the License
- Copyright notice: Each published work result is accompanied by an explicit statement of the license conditions for use. These are regularly typical conditions in connection with open source or free software. Programs described/provided/linked here are free software, unless otherwise stated.
- Permission notice: Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
- The copyright notice (Item 1) and the permission notice (Item 2) shall be included in all copies or substantial portions of the Software.
- The software is provided "as is" without warranty of any kind, either express or implied, including, but not limited to, the warranties of fitness for a particular purpose, merchantability, and/or non-infringement. The authors or copyright holders shall not be liable in any manner whatsoever for any damages or other claims arising from, out of or in connection with the software or the use or other dealings with the software, whether in an action of contract, tort, or otherwise.
- We take open source license compliance very seriously. We are always striving to achieve compliance at all times and to improve our processes. If you find any issues or have any suggestions or comments, or if you see any other ways in which we can improve, please reach out to: ospo@gematik.de
- Please note: Parts of this code may have been generated using AI-supported technology. Please take this into account, especially when troubleshooting, for security analyses and possible adjustments.
E-Mail to DEMIS Entwicklung