eHealth Platform Federal Core Profiles
2.0.1 - STU1
This page is part of the HL7 Belgium FHIR Implementation Guide - Core profiles (v2.0.1: Trial Use) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). 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 constraints on FHIR resources for systems conforming to this implementation guide
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. |
These define constraints on FHIR data types for systems conforming to this implementation guide
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
Care Location Value Set |
Care Location Value Set |
Patient Relationship Type Value Set |
Describes the patient relationship type (the relation between the patient and the person implied) |
be-civilstate |
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. |
be-contactperson |
Maximum valuest to define category of a contact person, using the HL7 values and the Belgian CD-CONTACT-PERSON values. |
These define new code systems used by systems conforming to this implementation guide
BeCSCareLocation |
Care Location Code System |
BeCdFedCountry |
FedICT country codes. |
BeCdCivilState |
Civil state in Belgium. |
BeCdContactPerson |
Contact person in Belgium. |
BeCdHcParty |
healthcare party in Belgium. |
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-organization |
Naming System - Nihdi - Organization |
be-ns-nihdi-professional |
Naming System - Nihdi - Professional |
be-ssin |
NISS/INSZ |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like
organization1 |
patient1 |
patient2 |
practitioner1 |
practitionerrole1 |
provenance1 |
relatedperson |