eHealth Platform Federal Core Profiles
2.1.2 - STU1
This page is part of the HL7 Belgium FHIR Implementation Guide - Core profiles (v2.1.2: 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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
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 |
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 (see also remark in Guidance ) |
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. |
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. |
BeCodedAnnotation |
Annotation DataType with added CodeableConcept extension element |
These define constraints on FHIR data types for systems conforming to this implementation guide.
BeExtCodeableConcept |
Extension with a CodableConcept |
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 ) |
BeExtGenderAtBirth |
Gender at the time of birth. The gender at birth has lasting consequences on clinical and medical level. |
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 |
These define sets of codes used by systems conforming to this implementation guide.
BeCivilState |
Civil State |
BeContactPerson |
Maximum valuest to define category of a contact person, using the HL7 values and the Belgian CD-CONTACT-PERSON values. |
BeVSCareLocation |
Care Location Value Set |
BeVSCdHcParty |
List of health care parties in Belgium |
BeVSPatientRelationshipType |
Describes the patient relationship type (the relation between the patient and the person implied) |
List of possible genders at birth in Belgium |
BeVSGenderAtBirth |
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. |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
BeCBENamingSystem |
BCE/KBO |
BeEhealthPartnerIDNamingSystem |
EHP |
BeInsuranceNumberNamingSystem |
the identification number of a mutual insurance association (mutualité) as “a not-for-profit association, which, with foresight, assistance and solidarity aims to promote the physical, mental and social well-being of its members” (The Belgian law of 6 August 1990) |
BeInsurancymembershipNamingSystem |
Membership number of a patient with an insurance organization |
BeNIHDINamingSystem |
RIZIV/INAMI |
BeNIHDINomenclatureNamingSystem |
NIHDI nomenclature (RIZIV-INAMI) |
BeNIHDIOrganizationNamingSystem |
Naming System - Nihdi - Organization |
BeNIHDIProfessionalNamingSystem |
Naming System - Nihdi - Professional |
BeSSINNamingSystem |
NISS/INSZ |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
coded-annotation |
Observation with coded annotation |
documentreferencebinary |
DocumentReference with binary file |
documentreferenceurl |
DocumentReference with external URL |
organization1 |
Belgian organization |
patient1 |
Belgian Patient |
patient2 |
Another Belgian Patient |
practitioner1 |
Belgian Practitioner with 11 digit NIHDI |
practitioner2 |
Belgian Practitioner with 8 digit NIHDI (deprecated) |
practitionerrole1 |
Belgian PractitionerRole |
provenance1 |
Belgian Provenance |
relatedperson |
Related Person, but with Belgium specific value set |