v2.1.0
draft
eReferral Implementation Guide
2.1.0 -
v2.1.0
draft
eReferral Implementation Guide
2.1.0 -
eReferral Implementation Guide, published by Riziv-Inami Platform. This guide is not an authorized publication; it is the continuous build for version 2.1.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
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.
| EReferralAnnex81 |
Annex81 proposal and approval |
| EReferralImagingAttentionConditionsResponse |
eReferral response to the imaging attention conditions questionnaire. |
| EReferralServiceRequestDiagnosticImaging |
The diagnostic imaging profile. eReferral version. |
| EReferralServiceRequestNursing |
The nursing profile, generic version. Please note the nursing referral for medication does NOT depend on this generic version but is a FHIR prodfile on a different FHIR resource (MedicationRequest) |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| CodeableConcept Extension for Reference |
Extension able to hold a coded concept on a Reference element. |
| eReferral Radiology SupportingInfo Role |
Identifies the role of a ServiceRequest.supportingInfo entry used in a diagnostic imaging referral. |
These define sets of codes used by systems conforming to this implementation guide.
| PSS/QSI Indication |
Indication codes for diagnostic imaging requests as PSS Internal Codes. |
| SNOMED CT eReferral Supplement Designations |
SNOMED CT supplement containing multilingual designations maintained for the eReferral project. |
| eReferral Imaging Patient Condition Indication |
Allowed coded indications for patient condition in diagnostic imaging. |
| eReferral Radiology SupportingInfo Role ValueSet |
Allowed roles for entries in ServiceRequest.supportingInfo in a diagnostic imaging referral. |
| eReferral/PSS Diagnostic Imaging Condition |
Clinical conditions that can support a diagnostic imaging request using SNOMED CT. |
| eReferral/PSS Diagnostic Imaging Procedure |
Diagnostic care services that can be prescribed for diagnostic imaging using SNOMED CT. |
These define new code systems used by systems conforming to this implementation guide.
| PSS Indication |
PSS indication codes for diagnostic imaging requests. |
| PSS/QSI Diagnostic Imaging Procedure |
PSS/QSI diagnostic imaging procedure codes with English displays and Belgian French, Dutch and German designations. |
| SNOMED CT eReferral Supplement Designations |
SNOMED CT supplement containing multilingual designations maintained for the eReferral project. |
| eReferral Designation Use |
Identifies terminology designations maintained specifically for the eReferral project. |
| eReferral Radiology SupportingInfo Role CodeSystem |
Identifies the role represented by an entry in ServiceRequest.supportingInfo for a diagnostic imaging referral. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example: Annex 81 - Preparing medication (proposal) |
Example of an Annex 81 ServiceRequest proposal for preparing medication. Inputs and values used in this example:
|
| Example: Bloodletting |
Example of therapeutic bloodletting including quantity. Inputs and values used in this example:
|
| Example: Chronic home dialysis |
Example of chronic home dialysis prescription. Inputs and values used in this example:
|
| Example: Diabetes education via convention centre |
Example of diabetes education delivered through a convention centre. Inputs and values used in this example:
|
| Example: Diabetes education within care trajectory |
Example of diabetes education within an established care pathway. Inputs and values used in this example:
|
| Example: Diabetes education within start trajectory |
Example of diabetes education within a start trajectory. Inputs and values used in this example:
|
| Example: Diabetes education without care trajectory |
Example of diabetes education for patients without a care trajectory. Inputs and values used in this example:
|
| Example: Diagnostic imaging referral |
Example of a diagnostic imaging referral prescription with contained patient and imaging attention questionnaire response. |
| Example: Generic nursing care |
Example of a generic nursing ServiceRequest. Inputs and values used in this example:
|
| Example: Glycemic control with glucometer |
Example of glycemic monitoring using a glucometer. Inputs and values used in this example:
|
| Example: Hygienic care |
Example of hygienic nursing care. Inputs and values used in this example:
|
| Example: Measurement of parameters |
Example of clinical parameter monitoring. Inputs and values used in this example:
|
| Example: Preparation of medicines (not refunded) |
Example of non-reimbursed medication prefill preparation. Inputs and values used in this example:
|
| Example: Prior diagnostic imaging referral |
A complete prior diagnostic imaging prescription referenced by the main diagnostic imaging example. |
| Example: Sample collection |
Example of a biological sample collection prescription. Inputs and values used in this example:
|
| Nurse |
Example practitioner acting as a nurse. |
| Nurse Requester |
Nurse acting as a Requester |
| Physician |
Example practitioner acting as a requesting physician. |
| Physician Requester |
Physician acting as a Requester |
| Urgency Physician Requester |
Urgency Physician acting as a Requester |
These are resources that are used within this implementation guide that do not fit into one of the other categories.
| ereferral-referral-task |
Example referral task associated with a nursing prescription. |
IG © 2026+ Riziv-Inami Platform.
Package inami.fhir.be.ereferral#2.1.0 based on FHIR 4.0.1.
Generated 2026-09-15
