Implementation Guide
TIFlow - Grenzüberschreitender Datenaustausch
Version 2.0.0-ballot.2 - ballot

## ValueSet: ValueSet of Consent Codes

Official URL: https://gematik.de/fhir/tiflow-xborder/ValueSet/GEM-ERPEU-VS-ConsentType | Version: 2.0.0-ballot.2
Draft as of 2026-06-30 | Computable Name: GEM_ERPEU_VS_ConsentType

Type of Consents for the ePrescription.

References

- Consent for ePrescriptions

### Logical Definition (CLD)

- Include all codes defined in `https://gematik.de/fhir/tiflow-xborder/CodeSystem/GEM-ERPEU-CS-ConsentType` version 📦2.0.0-ballot.2

### Expansion

Expansion performed internally based on codesystem CodeSystem of types for a consent v2.0.0-ballot.2 (CodeSystem)

This value set contains 1 concepts

System | Code | Display (de) | JSON | XML
`https://gematik.de/fhir/tiflow-xborder/CodeSystem/GEM-ERPEU-CS-ConsentType` | EUDISPCONS |  |  |

Explanation of the columns that may appear on this page:

Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System | The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code | The code (used as the code in the resource instance)
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition | An explanation of the meaning of the concept
Comments | Additional notes about how to use the code