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
Codesysteme
Die CodeSysteme sind in eines oder mehrere der Profile integriert, soweit sie jeweils relevant sind.
In der nachfolgenden Tabelle werden die im Rahmen dieses Leitfadens definierten CodeSysteme erläutert. Ggf. weitere verwendete CodeSysteme (z.B. FHIR Core-CodeSystems) sind im FHIR-Standard bzw. im jeweiligen Quell-Leitfaden dokumentiert.
| 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. |