v3.0.0 draft

eReferral Implementation Guide
3.0.0 - Belgium flag

eReferral Implementation Guide, published by Riziv-Inami Platform. This guide is not an authorized publication; it is the continuous build for version 3.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-be/referral-uhmep/ and changes regularly. See the Directory of published versions

eReferral Implementation Guide

Official URL: https://www.riziv-inami.be/standards/fhir/ereferral/ImplementationGuide/inami.fhir.be.ereferral Version: 3.0.0
Draft as of 2026-09-02 Computable Name: EReferral

This implementation guide defines the local eReferral FHIR profiles, examples, mappings, and guidance for referral prescriptions.




Important: migration from the DRP IG to the Referral IG is planned for the next release. Integrators must prepare to replace their DRP IG dependencies and references with the corresponding Referral IG artefacts. The final package versions, artefact mappings and transition arrangements remain to be confirmed in the release documentation.

Impacts for integrators
  • Review FHIR package dependencies and update IG configurations, validators and build pipelines to the published Referral package and its required versions.
  • Review inherited profiles, extensions, terminology bindings and constraints against the final DRP-to-Referral mapping; do not assume that migration is only a package rename.
  • Update affected profile declarations, extension URLs and other canonical references in resource generation, validation rules, mappings and examples where required by that mapping.
  • Revalidate representative nursing and radiology payloads and rerun integration and regression tests against the target release.
  • Assess handling of existing DRP-based resources and exchanges with partners still using DRP. Acceptance of legacy references and any coexistence period are not yet confirmed.

Important: the canonical base URL is planned to change. The current base https://www.riziv-inami.be/standards/fhir/ereferral/... will move to https://www.ehealth.fgov.be/standards/fhir/XXX/.... The final name replacing XXX remains to be defined. This is a placeholder, not a canonical URL to use in implementations. The effective release and final URL mapping remain to be confirmed.

Impacts for integrators
  • Inventory affected canonical references, including meta.profile, extension url values, profile inheritance and terminology references. Change only URLs covered by the final mapping; other namespaces are not automatically affected.
  • Update hard-coded URL comparisons, configuration, mappings, generated clients, examples and test fixtures that depend on the current canonical base.
  • Reload the target packages in validators and canonical resolvers, review caches and verify that the new URLs resolve to the intended artefact versions.
  • For affected CodeSystems, assess the impact on Coding.system, persisted coded data and terminology services. Do not bulk-rewrite historical resources without an agreed migration policy.
  • Do not assume redirects or automatic equivalence between old and new canonicals. Legacy URL acceptance remains to be confirmed. A canonical namespace change does not by itself announce a change to the operational FHIR API endpoint.



This documentation and set of artefacts are still undergoing development.
The canonical URL and publication address of this Implementation Guide are provisional and subject to change.
This Implementation Guide contains only demonstrative examples of terminology resources. ValueSets and CodeSystems in this Implementation Guide are provided as examples only. The actual ValueSets and CodeSystems will be made available from a terminology package and can then be consulted in the FHIR terminology ecosystem.
Technical scope only. This Implementation Guide has a technical purpose: it helps integrators implement the eReferral FHIR API. It does not define, and is not the guarantor of, the business rules (eligibility, reimbursement, therapeutic-relationship, consent, or other INAMI-defined business logic). For business rules, integrators must always refer to INAMI/RIZIV.

The current scope is focused on:

Domain Main content
Nursing Generic nursing ServiceRequest prescriptions and Annex 81 proposal/approval flows.
Radiology Diagnostic imaging ServiceRequest prescriptions and the imaging attention conditions response.
Cross-domain Pseudonymization rules, validity and feedback extensions, requester/subject handling, and example validation.

What This IG Contains

Section Purpose
Guidance Implementation rules and modelling choices used across the local profiles.
Migration 2.1.0 to 3.0.0 Payload compatibility checks, radiology transitions, terminology baseline and regression tests.
API Integration Authentication, identifiers, pseudonymization, validations, and errors.
API Operations Operation-by-operation map, with allowed roles and links to the error-code workbook.
Access Matrix Roles, INAMI access matrix, suspension, and search-filter access control.
Life Cycle Business↔FHIR status mapping, lifecycle and task diagrams, proposal life cycle, and prescription extension.
Prescription Templates Technical-identifier catalogue, profiles, and validity rules per template.
Visibility & Blacklisting Template visibility, blacklisting behaviour, and cancelled-prescription rules.
Business Field Mappings Business field to FHIR mappings, grouped by domain and prescription type.
Artifacts Generated FHIR profiles, extensions, ValueSets, CodeSystems, and examples.
Technical Entry points, required headers, reference documents, support contacts, and certificates.
Glossary Terminology used across this IG.
Downloads Downloadable packages and generated resources.
Changes Change notes for this local IG.

Profiles

Profile Purpose
eReferralServiceRequestNursing Generic nursing ServiceRequest prescriptions.
eReferralAnnex81 Annex 81 nursing medication preparation proposal/approval.
eReferralServiceRequestDiagnosticImaging Diagnostic imaging ServiceRequest prescriptions.
eReferralImagingAttentionConditionsResponse Contained response for radiology attention/safety checklist information.

Business Mappings

The IG includes mapping pages generated from the nursing template Excel. These pages map business fields and allowed values to proposed FHIR elements and candidate terminologies.

Start with:

Domain Page
Nursing Nursing mappings
Radiology Radiology mappings

Terminology notes in the mapping pages are intentionally conservative. Some Excel value lists predate the current ValueSets and may require reconciliation before being treated as normative coded values.