Clinical Core, published by eHealth Platform. This guide is not an authorized publication; it is the continuous build for version 1.4.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-clinical/ and changes regularly. See the Directory of published versions

Transversal Clinical Core

Official URL: https://www.ehealth.fgov.be/standards/fhir/core-clinical/ImplementationGuide/hl7.fhir.be.core-clinical				Version: 1.4.0	Highlight text changes?
Active as of 2026-10-16					Computable Name: TransversalClinicalCore
Other Identifiers: OID:2.16.840.1.113883.4.642.40.200.5

This is the Belgian Core Clinical FHIR Implementation Guide. It contains the clinical specifications developed by our community that can be reused in other implementation guides.

Content

This IG is structured in the following content sections:

Background: Information about the specifications, or what you should know to be able to best navigate and use these specifications. Contains a general introduction to the publication structure and content, the artefact types, common privacy and security specifications and the official HL7 FHIR release that this specification is based upon.

Functional Description: Functional content, more relevant for business or functional analysts, as well as health professionals. Contains the context around these specifications (relevant projects, legal and implementation aspects), the interoperability actors and transactions, and especially the use cases that have been considered in the specification and the logical data models – the functional (i.e. non-technical) data sets that are used in data exchange.

Detailed Specifications: The actual technical specifications – the FHIR conformance resources that are defined in this specification – profiles, data types, capability statements. This is targeted at (technical) implementers.

Terminology: The vocabulary resources – Naming Systems, Code Systems and Value Sets, which support semantic interoperability. These resources define the use of standard terminologies (e.g. LOINC, SNOMED-CT) or internal codes for Belgium, e.g. official codes for Civil Status).

The top menu allows quick navigation to the different sections, and a Table of Contents is provided with the entire content of this Implementation Guide. (Be aware that some pages have multiple tabs).

Dependencies

This IG Contains the following dependencies on other IGs.

Package hl7.fhir.uv.extensions.r4#5.4.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Wed, Oct 28, 2026 08:43+1100+11:00)

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00)

Package hl7.fhir.be.core#2.2.0 eHealth Platform Federal Core Profiles (built Wed, Aug 19, 2026 10:40+0200+02:00)

Package hl7.fhir.uv.xver-r5.r4#0.1.0 Extensions for Using Data Elements from FHIR R5 in FHIR R4 (built Fri, Mar 20, 2026 15:40+1100+11:00)

Package hl7.fhir.uv.tools.r4#1.3.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Oct 6, 2026 15:55+1100+11:00)

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.be.core-clinical.r4) and R4B (hl7.fhir.be.core-clinical.r4b) are available.

Intellectual Property

This publication includes IP covered under the following statements.

• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): BeDevice, BeDeviceUseStatement... Show 15 more, BeExtBodyTopography, BeExtLaterality, BeModelDevice, BeModelDeviceUseStatement, BeModelProblem, BeProblem, BeScoreResult, BeVSBodySite, BeVSBodyTopography, BeVSLaterality, BeVSReactionManifestationCode, BeVSScore, BeVSSeverity, DeviceTypeVS and ProblemDiseaseCourseVS
• This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  • Condition Clinical Status Codes: BeModelProblem
  • ConditionVerificationStatus: BeModelProblem
  • FHIRDeviceStatusReason: BeModelDevice and DeviceStatusReasonVS
  • Service type: BeEncounter