eHealth Platform Federal infsec Profiles
1.2.0 - STU1 Belgium flag

This page is part of the eHealth FHIR Infrastructure and Security Profiles for Belgium (v1.2.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Intended profile

Using this extension, the sender indicates that he intends this resource to comply with the profile and version mentioned here. This profile will be used to determine the semantic integrity of the profile.
Key Pseudonymization Extension

This holds a pseudonymized key that can be used for all encrypted fields in the resource (long text pseudonymisation)
Pseudonymization Extension

This is a marker interface. If the field is pseudonymized, the string field SHALL have this extension.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Types of pseudonymization

The technique used for pseudonymization

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

BeCSPseudonymizationVersion

List of pseudonymization versions that can be used a.o. in the Capabilities Statement
Types of pseudonymization

The technique used for pseudonymization

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Bundle with pseudonymisation examples

Each resource in the bundle has its own pseudo-encryption key
Capability Statement with Pseudonymisation

This capability statement contains the entries to indicate that you support pseudo v1 and v2 and pseudo-encryption v1.
Contained resource with long text pseudonymisation

Example of a contained resource, which always has its own pseudonymisation key if long text pseudonymisation is applied.
Parameters object with long text encryption and key

Long text encryption for resources which are not domain resources
Patient with v1 Pseudonymisation

Example of v1 Pseudonymisation without prefix
Patient with v2 Pseudonymisation and long text pseudonymisation

Example of a domain resource containing both direct and encrypted pseudonymisation