2025.2.0 - ci-build
IGTTPFHIRGatewayTerminologie - Local Development build (v2025.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Artifacts Summary
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
Terminology: Value Sets
These define sets of codes used by systems conforming to this implementation guide.
| BloomfilterType |
Types of Bloomfilters. (DRAFT) |
| ConsentComponentType |
Types of consent components relevant to gICS for differentiation as a search criterion |
| ConsentPolicyAction |
Extensible description of the permissible (data processing-) action resulting from consented module or policy. |
| ConsentPolicyActor |
Expandable categorisation of consumer/requestor of a consent enforcement request related to a specific consent component (e.g. policy or module) |
| ConsentPolicyClass |
Extensible description of the application perspective of a ConsentPolicy (e.g. selected data view 'IDAT') |
| ConsentPolicyPurpose |
Expandable specification of the application context and/or scope of a consent policy or module |
| ConsentStatus |
consent states are used to depict the participant’s will. Therefore, documentation should allow different status values. Further details from https://doi.org/10.1186/s12967-020-02457-y |
| ConsentStatusConsentFullValues |
consent states - subset CONSENT documents |
| ConsentStatusConsentOptOutFullValues |
consent states - subset OPT-OUT-CONSENT documents |
| ConsentStatusConsentOptOutShortValues |
consent states - minimal subset OPT-OUT-CONSENT documents |
| ConsentStatusConsentShortValues |
consent states - minimal subset CONSENT documents |
| ConsentStatusObjectionFullValues |
consent states - subset OBJECTION documents |
| ConsentStatusObjectionShortValues |
consent states - minimal subset OBJECTION documents |
| ConsentStatusRefusalFullValues |
consent states - subset REFUSAL documents |
| ConsentStatusRefusalShortValues |
consent states - minimal subset REFUSAL documents |
| ConsentStatusWithdrawalFullValues |
consent states - subset WITHDRAWAL documents |
| ConsentStatusWithdrawalShortValues |
consent states - minimal subset WITHDRAWAL documents |
| IdMatchingType |
ID matching types used in consent management |
| IdatElements |
Element names for use in $requestTasks operation. |
| MatchStatus |
Possible match statuses in the context of adding patient identities. |
| Policy |
common consent policies used in consent management in medical research |
| PolicyStatus |
set of policy status states used for consent management |
| SaveAction |
Possible save actions in the context of adding patient identities. |
Terminology: Code Systems
These define new code systems used by systems conforming to this implementation guide.
| BloomfilterType |
Types of Bloomfilters. |
| ConsentComponentType |
Typen der für gICS relevanten Consent-Componenten zur Unterscheidung als Suchkriterium |
| ConsentPolicyAction |
Extensible description of the permissible (data processing-) action resulting from consented module or policy. |
| ConsentPolicyActor |
Expandable categorisation of consumer/requestor of a consent enforcement request related to a specific consent component (e.g. policy or module) |
| ConsentPolicyClass |
Extensible description of the application perspective of a ConsentPolicy (e.g. selected data view 'IDAT') |
| ConsentPolicyPurpose |
Expandable specification of the application context and/or scope of a consent policy or module |
| ConsentStatus |
consent states are used to depict the participant’s will. Therefore, documentation should allow different status values. Further details from https://doi.org/10.1186/s12967-020-02457-y |
| DesignationUse |
Use codes (contexts) for terminology designations |
| IdMatchingType |
ID matching types used in consent management |
| IdatElements |
Element names for use in $requestTasks operation. |
| MatchStatus |
Possible match statuses in the context of adding patient identities. |
| Policy |
Policies used in consent management |
| SaveAction |
Possible save actions in the context of adding patient identities. |