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

## ValueSet: ValueSet of Consent PolyRule Codes

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

Type of Policy Rules for Consents of the ePrescription.

References

- Consent for ePrescriptions

### Logical Definition (CLD)

- Include these codes as defined in `http://terminology.hl7.org/CodeSystem/v3-ActCode` version 📍10.0.0

  Code | Display | Definition
  OPTIN | opt-in | A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. *Comment:* Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. *Usage Note:* Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". **Examples:** * Healthcare: A patient \[grantor\] signs a provider's \[grantee's\] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies. * Non-healthcare: An employee \[grantor\] signs an employer's \[grantee's\] non-disclosure and non-compete agreement.

### Expansion

Expansion performed internally based on codesystem ActCode v10.0.0 (CodeSystem)

This value set contains 1 concepts

System | Code | Display (de) | Definition | JSON | XML
`http://terminology.hl7.org/CodeSystem/v3-ActCode` | OPTIN | opt-in | A grantor's assent to the terms of an agreement offered by a grantee without an opportunity for to dissent to any terms. Comment: Acceptance of a grantee's terms pertaining, for example, to permissible activities, purposes of use, handling caveats, expiry date, and revocation policies. Usage Note: Opt-in with no opportunity for a grantor to restrict certain permissions sought by the grantee is considered "basic consent". Examples: Healthcare: A patient [grantor] signs a provider's [grantee's] consent directive form, which lists permissible collection, access, use, or disclosure activities, purposes of use, handling caveats, and revocation policies. Non-healthcare: An employee [grantor] signs an employer's [grantee's] non-disclosure and non-compete agreement. |  |

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