Creates an approval from an Annex81 proposal

Rejects an Annex81 proposal

Specify to include all useful resources around a ServiceRequest that can be retrieved with the $graph operation.

Logical model describing the model for the Annex81 proposal and approval

Logical model with the information for the assignment to a referral prescription of a care provider.

Data model for the nursing prescription referral.

Information of a claim of an organisation to have the prescription fulfilled.

Data model for the prescription referral.

Logical model with the information for the status of the treatment.

Questionnaire for capturing attention-worthy conditions relevant to diagnostic imaging requests (implants, pregnancy, diabetes, allergies, etc.)

Annex81 proposal and approval

Response to the imaging attention conditions questionnaire. At least one attention condition must be answered.

Subtask to assign the referral task and prescription to one or more members of this organisation

Subtask performed by one performer

The common structure for referral prescription.

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)

The task that is referred to in the referral prescription (this is the common task for the execution of the prescription). The subtasks per performer can be found in BePerformerTask

The diagnostic imaging profile. Generic version.

Whether the prescriber requests feedback on the processing of the order

Request must be performed before

Information regarding the Prescription Search Support

Types of performers that can execute this request

Relevant clinical information in the context of this prescription concerning for example allergies, kidney function, diabetic. This extension allows the use of an Annotation or codeableConcept but when more detailed information can be given, it is RECOMMENDED to express it as structured as possible using the appropriate elements.

Justification for the urgency level assigned to the request

Begin and end date of the validity of the request

Extension able to hold a coded concept on a Reference element.

Indicates the role of a supporting information item in an eReferral for radiology.

Date represented as a string. This extension is used to capture date information in a string format when a date must be encrypted.

DEMONSTRATIVE EXAMPLE - Status reason of the Annex 81

eReferral reasons for the status of the prescription

eReferral allowed intent codes in the context of referral prescription

DEMONSTRATIVE EXAMPLE - The allowed intent codes in the context of tasks in the field of referral prescriptions

DEMONSTRATIVE EXAMPLE - Codes for the current status of a treatment in a referral prescription.

Indication codes for diagnostic imaging requests as PSS Internal Codes.

Clinical care services for Annex 81 prescriptions.

Medical problems/conditions that can justify an Annex 81 request.

Nursing diagnoses/findings that can motivate an Annex 81 request.

Technical type for Annex 81 prescriptions.

Anatomical body sites based on SNOMED CT for use in referral prescriptions.

Topographical qualifiers for body sites based on SNOMED CT.

Categories of care that can be prescribed by a GP in the eReferral project. Currently limited to nursing care.

Identifiers to distinguish types of diabetes education prescriptions.

Types of diabetes education for education within a care trajectory.

Types of diabetes education for patients without a trajectory.

Types of educators for diabetes education activities.

Timing of glycemia measurements.

Allowed modalities for imaging requests.

Allowed priorities for imaging requests.

Allowed implant types.

Types of notes that can be associated with a referral prescription.

Clinical care services that can be prescribed for nursing care using SNOMED CT.

Technical types of nursing prescriptions for routing and workflow purposes.

Types of parameters/vital signs that can be measured.

Technical types of prescriptions supported by the eReferral system. Used for routing and workflow purposes.

Defines the set of roles that supporting information can have in an eReferral for radiology.

Types of samples/substances that can be collected.

Types of sessions for education or care activities (standard).

Types of sessions for education or care activities (extended, including combination).

Allowed request tracks. Extends the official Belgian request track value set with UHMEP-specific codes.

Clinical indications and findings that can support a diagnostic imaging request using SNOMED CT.

Diagnostic care services that can be prescribed for diagnostic imaging using SNOMED CT.

DEMONSTRATIVE EXAMPLE - Status reason for the prescription. Initially defined as supporting CodeSystem for the referral prescription.

DEMONSTRATIVE EXAMPLE - Status reason for the treatment. Initially defined as supporting CodeSystem for the referral prescription.

PSS indication codes for diagnostic imaging requests.

DEMONSTRATIVE EXAMPLE - Status reason for the Annex 81

Types of diabetes education activities.

Types of care that can be prescribed via the generic prescription.

Timing of glycemia measurements.

Imaging modality types for prior imaging requests

Priority codes for diagnostic imaging requests

Types of notes that can be associated with a prescription.

Technical types of prescriptions supported by the eReferral system. Used for routing and workflow purposes.

Defines the codes representing the roles of supporting information in an eReferral for radiology.

Care setting track codes for diagnostic imaging requests

Types of sessions for education or care activities.

Naming system identifier for the UHMEP user friendly short code

PSS ID naming system

UHMEP naming system

Terminology expansion parameters used to include designations.