This page is part of the eHealth FHIR Referral Prescription Profiles for Belgium (v1.0.0: Release) based on FHIR (HL7® FHIR® Standard) 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

Home

Official URL: https://www.ehealth.fgov.be/standards/fhir/referral/ImplementationGuide/hl7.fhir.be.referral				Version: 1.0.0	Highlight text changes?
Active as of 2026-08-21					Computable Name: ReferralPrescription

This is the HL7 Belgium FHIR Implementation Guide for the Referral prescription workgroup.
General guidance is available on the Guidance page \

Content

This publication contains the specifications related to the referral prescription areas and is structured in the following content sections:

Background:
Information about the HL7 Belgium 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 - Code Systems and value sets, that support semantic interoperability. These resources promote the use of standard, controlled terminologies (e.g. SNOMED-CT) and define internal codes for Belgium, e.g. official codes for Civil Status).

Implementation:
Content, Tools and resources to help in implementation - test data (example resources), currently available test servers, and other tools to validate the compatibility between systems and these specifications.

There is also an overview of the projects and motivation for the specifications.

---

Navigation

This implementation guide uses the FHIR web-based publication. This allows easy navigation between the Belgium-specific portion of the implementation guide and the resources, data types, value sets and other specification components leveraged from the FHIR core specification. This approach also allows implementers to easily navigate to the information needed to perform a task.

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.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 Thu, Aug 13, 2026 15:32+0200+02:00)

Package hl7.fhir.uv.extensions.r4#5.1.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, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.be.core#2.1.2 eHealth Platform Federal Core Profiles (built Fri, Aug 30, 2024 17:07+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.be.core-clinical#1.3.0 HL7 Belgium - Transversal Clinical Core (built Thu, Aug 13, 2026 15:28+0200+02:00)

Package hl7.fhir.be.infsec#1.3.0 eHealth Platform Federal infsec Profiles (built Fri, Jun 26, 2026 09:52+0200+02:00)

Package hl7.fhir.uv.tools.r4#1.1.2 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, Mar 24, 2026 11:13+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.referral.r4) and R4B (hl7.fhir.be.referral.r4b) are available.

Global Profiles

There are no Global profiles defined

Expansion Parameters

Parameter	Value
includeDesignations	true
system-version	SNOMED CT[BE]

Intellectual Property Considerations

While this implementation guide and the underlying FHIR are licensed as public domain, this guide includes examples making use of terminologies such as LOINC, SNOMED CT and others which have more restrictive licensing requirements. Implementers should make themselves familiar with licensing and any other constraints of terminologies, questionnaires, and other components used as part of their implementation process. In some cases, licensing requirements may limit the systems that data captured using certain questionnaires may be shared with.

This publication includes IP covered under the following statements.

• ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  • ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: Approve, BeAnnex81... Show 77 more, BeCSAnnex81StatusReason, BeCSGenericCareTypes, BeCSGlycemiaMeasurementTiming, BeCSImagingModality, BeCSImagingPriority, BeCSNoteTypes, BeCSPSSIndication, BeCSPrescriptionType, BeCSRadiologySupportingInfoRole, BeCSRequestTrack, BeCSSessionTypes, BeCSdiabeticEducationType, BeExtCodeableConcept, BeFeedbackToPrescriber, BeImagingAttentionConditionsResponse, BeLatestEndDate, BeModelAnnex81, BeModelAssignment, BeModelNursingPrescription, BeModelOrganisationClaim, BeModelReferralPrescription, BeModelTreatmentStatus, BeNsUhmepShort, BeOrganizationTask, BePSSId, BePSSInfo, BePerformerTask, BePerformerType, BePrescriptionStatusReason, BeQuestionnaireImagingAttentionConditions, BeRadiologySupportingInfoRole, BeReferralServiceRequest, BeReferralServiceRequestNursing, BeReferralTask, BeRelevantInfo, BeServiceRequestDiagnosticImaging, BeStringDate, BeTreatmentStatusReason, BeUnadressedHealthMessageExchangePlatform, BeUrgencyJustification, BeVSAnnex81CareRequested, BeVSAnnex81MedicalProblem, BeVSAnnex81NursingDiagnosis, BeVSAnnex81StatusReason, BeVSAnnex81TechnicalType, BeVSBodySite, BeVSBodyTopography, BeVSCategoriesOfCare, BeVSDiabetesEducationIdentifier, BeVSDiagnosticImagingIndication, BeVSDiagnosticImagingProcedure, BeVSEducationTypeWithTrajectory, BeVSEducationTypeWithoutTrajectory, BeVSEducatorType, BeVSGlycemiaMeasurementTime, BeVSImagingModality, BeVSImagingPriority, BeVSImplantType, BeVSNoteTypes, BeVSNursingCareRequested, BeVSNursingPrescriptionTechnicalType, BeVSPSSIndication, BeVSParameterType, BeVSPrescriptionStatusReason, BeVSPrescriptionType, BeVSRadiologySupportingInfoRole, BeVSRequestIntent, BeVSRequestTrack, BeVSSampleSubstanceType, BeVSSessionType, BeVSSessionTypeExtended, BeVSTaskIntent, BeVSTreatmentStatusReason, BeValidityPeriod, FullReferralPrescription, ReferralPrescription and Reject
• 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®): BeAnnex81, BeQuestionnaireImagingAttentionConditions... Show 17 more, BeReferralServiceRequest, BeReferralServiceRequestNursing, BeServiceRequestDiagnosticImaging, BeVSAnnex81CareRequested, BeVSAnnex81MedicalProblem, BeVSAnnex81NursingDiagnosis, BeVSBodySite, BeVSBodyTopography, BeVSCategoriesOfCare, BeVSDiabetesEducationIdentifier, BeVSDiagnosticImagingIndication, BeVSDiagnosticImagingProcedure, BeVSEducatorType, BeVSImplantType, BeVSNursingCareRequested, BeVSParameterType and BeVSSampleSubstanceType

---

Disclaimer

The specification herewith documented is a first working specification. Implementers are requested to provide feedback on its implementation.