eHealth Platform Federal Core Profiles
2.1.0 - STU1 Belgium flag

eHealth Platform Federal Core Profiles, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/core/ and changes regularly. 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: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

BeModelPatient

Data about a patient, according to the National Register of Persons (Ministry of the Interior), and possibly other sources to be mentioned when used.
BeModelPatientDocument

Data about a patient related document

Structures: Resource Profiles

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

BeCommunication

Belgian federal profile on Communication
BeDocumentReference

Belgian federal profile on DocumentReference
BeOrganization

Belgian federal profile for an organization. Initially based on the functional description of the NIHDI.
BePatient

Belgian federal profile for a patient. Initially based on the functional description of the NIHDI. Special remarks for KMEHR users: following elements in KMEHR are not available in this FHIR resource. If needed, an extension can be defined in a future iteration of these specifications: the ‘deathlocation’ (location is not available but the death of the patient is expressed by either date or Boolean cfr. infra.), the ‘insurancystatus’ (covered in a seperate FHIR resource: Coverage), ‘insurancymembership’ (covered in a seperate FHIR resource: Coverage) and ‘profession’ (covered in a possible future FHIR resource: OccupationalData.)
BePractitioner

Belgian federal profile for a practitioner. Initially based on the functional description of the NIHDI.
BePractitionerRole

Belgian federal profile for a practitioner role. Initially based on the functional description of the NIHDI.
BeProvenance

Belgian federal profile for a provenance. Note this profile does not introduce any changes from the base profile but has been created to mark its importance, specifically when FHIR is used in a non-document approach. General use case remarks: ‘Provenance of a resource is a record that describes entities and processes involved in producing and delivering or otherwise influencing that resource.’ (cfr. the HL7 base specifications) According to the FHIR specifications, the provenance resource SHALL only be provided when no other resource already plays this role: for a Patient it SHOULD be its managing organization, provenance of an Observation SHOULD be its performer, provenance of an AllergyIntolerance SHOULD be its recorder. ‘Many other FHIR resources contain some elements that represent information about how the resource was obtained, and therefore they overlap with the functionality of the Provenance.’ Special remarks for KMEHR users: The FHIR Provenance resource in general refers to an entity that had something to do with the creation or updating of something else. In a KMEHR context, this is somewhat different – as it is ‘XML document’ based, each KMEHR message has an ‘author’ element that is responsible.

Structures: Data Type Profiles

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

BeAddress

Belgain federal profile on address, to provide the possibility in the ‘line’ element to provide a seperate streetname, housenumber and postal box. It is always RECOMMENDED to give these elements seperately.
Coded Annotation

Annotation DataType with added CodeableConcept extension element

Structures: Extension Definitions

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

BeExtCodeableReference

Extension able to hold a reference and a concept (Temporary solution until https://jira.hl7.org/browse/FHIR-44661 is solved and see Zulip: https://chat.fhir.org/#narrow/stream/179280-fhir.2Finfrastructure-wg/topic/Backporting.20CodeableReference )
BeExtRecorder

The recorder of the information - note that this may not always be the same as the asserter - when a patient reports to a nurse and the nurse enters the data, the asserter is the patient, but the recorder is the nurse
BeExtSimpleNote

Simple note extension if the element doesn’t have a note
CodeableConcept Extension

Extension with a CodableConcept

Terminology: Value Sets

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

Care Location Value Set

Care Location Value Set
Civil State

Codes supported by eHealth Platform differentiating types of civil state. This valueset supports the Belgian federal FHIR profiling effort. Whenever possible add a code from http://terminology.hl7.org/CodeSystem/v3-MaritalStatus for international interoperability but also use https://www.ehealth.fgov.be/standards/fhir/core/CodeSystem/CD-CIVILSTATE for the Belgian specific code.
ContactPerson

Maximum valuest to define category of a contact person, using the HL7 values and the Belgian CD-CONTACT-PERSON values.
List of health care parties in Belgium

List of health care parties in Belgium
Patient Relationship Type Value Set

Describes the patient relationship type (the relation between the patient and the person implied)

Terminology: Code Systems

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

BeCSCareLocation

Care Location Code System
BeCdCivilState

Civil state in Belgium.
BeCdContactPerson

Contact person in Belgium.
BeCdFedCountry

FedICT country codes.
BeCdHcParty

healthcare party in Belgium.

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

be-cbe

BCE/KBO
be-ehp

EHP
be-insurancenumber

insurance number
be-insurancymembership

Membership number of a patient with an insurance organization
be-nihdi

RIZIV/INAMI
be-ns-nihdi-nomenclature

NIHDI nomenclature (RIZIV-INAMI)
be-ns-nihdi-organization

Naming System - Nihdi - Organization
be-ns-nihdi-professional

Naming System - Nihdi - Professional
be-ssin

NISS/INSZ

Example: Example Instances

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

coded-annotation
documentreferencebinary
documentreferenceurl
organization1
patient1
patient2
practitioner1
practitionerrole1
provenance1
relatedperson