0.1.0 - ci-build
EUAITransparencyIG - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Official URL: http://example.org/fhir/eu-ai-transparency/ValueSet/gdpr-art6-legal-basis-vs | Version: 0.1.0 | |||
| Active as of 2026-06-18 | Computable Name: GDPR_Art6_LegalBasisVS | |||
Value set including GDPR Article 6 legal bases relevant for documenting the lawful processing of personal data.
References
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem version 📦0.1.0
Expansion performed internally based on codesystem GDPR Article 6 Legal Basis CodeSystem v0.1.0 (CodeSystem)
This value set contains 6 concepts
| System | Code | Display (en) | JSON | XML |
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-a | Consent (Art. 6(1)(a)) | ||
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-b | Contract (Art. 6(1)(b)) | ||
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-c | Legal Obligation (Art. 6(1)(c)) | ||
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-d | Vital Interests (Art. 6(1)(d)) | ||
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-e | Public Interest or Official Authority (Art. 6(1)(e)) | ||
http://example.org/fhir/eu-ai-transparency/CodeSystem/gdpr-art6-codesystem | gdpr-art-6-1-f | Legitimate Interests (Art. 6(1)(f)) |
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 |