IP Review

Unattributed Code Systems

http://dsf.dev/fhir/CodeSystem/read-access-tag

Copyright Fragment

This fragment is not visible to the reader

No use of external IP (other than from the FHIR specification)

Copyright and Registered Trademark Uses

IG © 2023+ DSF Community. Package dev.dsf#2.0.0 based on FHIR 4.0.1. Generated 2025-06-06 Links: Table of Contents | QA Report ( src )
hl7.fhir.us.hai: Healthcare Associated Infection Implementation Guide ®© HL7 | CC0 ( src )
Data Sharing Framework (DSF) Implementation Guide - Local Development build (v2.0.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions ( src )

External References

Type Reference Content

Type	Reference	Content
web	dsf.dev
web	dsf.dev	IG © 2023+ DSF Community . Package dev.dsf#2.0.0 based on FHIR 4.0.1 . Generated 2025-06-06 Links: Table of Contents \| QA Report
web	www.omg.org	Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )
web	browser.ihtsdotools.org	QuestionnaireAnswerCodes (a valid code from SNOMED CT ) `http://hl7.org/fhir/ValueSet/questionnaire-answers` From the FHIR Standard
web	github.com	ActivityDefinitions are used by the DSF to advertise which processes are available at any given instance and who is allowed to request and who is allowed to execute a process. The DSF defined elements for this purpose in the dsf-activity-definition profile.
web	www.gesundheitsforschung-bmbf.de	The Data Sharing Framework (DSF) is a concept for a secure middleware to distribute data sharing processes based on the BPMN 2.0 and FHIR R4 standards. The DSF is used to support biomedical research with routine data, aiming to extract, merge, pseudonymize and provide data stored in multiple distributed organizations. Every participating site runs a FHIR endpoint accessible by other sites and a business process engine in the local secured network. The process engines execute BPMN processes in order to coordinate local and remote steps necessary to enable cross-site data sharing or feasibility analyses. This includes access to local data repositories, use-and-access-committee decision support, consent filtering, and privacy preserving record-linkage and pseudonymization. The aim is to enable secure and syntactically-, semantically- and process-interoperable data exchange across organizational boundaries. The secure communication infrastructure is funded by the German Federal Ministry of Education and Research within the Medical Informatics structure as DSF Community .
web	github.com	The FHIR Task resource enables the DSF's distributed communication. Whenever a BPMN process instance communicates with a different process instance, the DSF will create a Task resource based on parameters you set in the BPMN model and during execution. It will then automatically send the Task resource to the recipient to start or continue whatever process the Task resource referred to. All Task resources used in the DSF derive from the dsf-task-base . This profile includes a splicing for `Task.input` with three additional Input Parameters:
web	github.com	When creating your own plugin, you will want to create your own profiles based on the dsf-task-base and put them into `src/resources/fhir/StructureDefinition` .
web	github.com	Task Input Parameters allow you to add additional information to Task resources. For example, if your particular data exchange requires additional medical data, you would add a slice to your Task profile in the same way the dsf-task-base adds slices to the original FHIR Task resource. Notice that this also requires creating a CodeSystem and including it in a ValueSet to be able to use it in the Task resource.
web	github.com	Task Output Parameters server a similar purpose to Task Input Parameters. They add additional information to a Task resource, but for a different context. While Task Input Parameters provide additional information which is required to process the Task, Task Output Parameters provide information on the Task's completion. For example, in the context of a voting process, you might add the results of the vote as a Task Output Parameter. You would add a slice to your Task profile in the same way the dsf-task-base adds slices to the original FHIR Task resource. Notice that this also requires creating a CodeSystem and including it in a ValueSet to be able to use it in the Task resource.

web

dsf.dev

web dsf.dev IG © 2023+ DSF Community . Package dev.dsf#2.0.0 based on FHIR 4.0.1 . Generated 2025-06-06
Links: Table of Contents | QA Report

web www.omg.org Mappings for ServD ( http://www.omg.org/spec/ServD/1.0/ )

web

browser.ihtsdotools.org

QuestionnaireAnswerCodes (a valid code from SNOMED CT )

http://hl7.org/fhir/ValueSet/questionnaire-answers

From the FHIR Standard

web github.com ActivityDefinitions are used by the DSF to advertise which processes are available at any given instance and who is allowed to request and who is allowed to execute a process. The DSF defined elements for this purpose in the dsf-activity-definition profile.

web www.gesundheitsforschung-bmbf.de The Data Sharing Framework (DSF) is a concept for a secure middleware to distribute data sharing processes based on the BPMN 2.0 and FHIR R4 standards. The DSF is used to support biomedical research with routine data, aiming to extract, merge, pseudonymize and provide data stored in multiple distributed organizations. Every participating site runs a FHIR endpoint accessible by other sites and a business process engine in the local secured network. The process engines execute BPMN processes in order to coordinate local and remote steps necessary to enable cross-site data sharing or feasibility analyses. This includes access to local data repositories, use-and-access-committee decision support, consent filtering, and privacy preserving record-linkage and pseudonymization. The aim is to enable secure and syntactically-, semantically- and process-interoperable data exchange across organizational boundaries. The secure communication infrastructure is funded by the German Federal Ministry of Education and Research within the Medical Informatics structure as DSF Community .

web github.com The FHIR Task resource enables the DSF's distributed communication. Whenever a BPMN process instance communicates with a different process instance, the DSF will create a Task resource based on parameters you set in the BPMN model and during execution. It will then automatically send the Task resource to the recipient to start or continue whatever process the Task resource referred to. All Task resources used in the DSF derive from the dsf-task-base . This profile includes a splicing for Task.input with three additional Input Parameters:

web github.com When creating your own plugin, you will want to create your own profiles based on the dsf-task-base and put them into src/resources/fhir/StructureDefinition .

web github.com Task Input Parameters allow you to add additional information to Task resources. For example, if your particular data exchange requires additional medical data, you would add a slice to your Task profile in the same way the dsf-task-base adds slices to the original FHIR Task resource. Notice that this also requires creating a CodeSystem and including it in a ValueSet to be able to use it in the Task resource.

web github.com Task Output Parameters server a similar purpose to Task Input Parameters. They add additional information to a Task resource, but for a different context. While Task Input Parameters provide additional information which is required to process the Task, Task Output Parameters provide information on the Task's completion. For example, in the context of a voting process, you might add the results of the vote as a Task Output Parameter. You would add a slice to your Task profile in the same way the dsf-task-base adds slices to the original FHIR Task resource. Notice that this also requires creating a CodeSystem and including it in a ValueSet to be able to use it in the Task resource.

Internal Images

tree-filter.png