Referral Prescription
1.0.0 - STU Belgium flag

Referral Prescription, published by . This guide is not an authorized publication; it is the continuous build for version 1.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/ and changes regularly. See the Directory of published versions

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

be-op-cancel

Cancel Referral Prescription or Proposal

Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

BeSPServiceRequestStatusReason

This SearchParameter enables query of ServiceRequests by the statusReason extension.

BeSPTaskStatusProfile

This SearchParameter enables query of Tasks on the combination of status and profile

Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

BeDiagnosticImagingPrescription

Logical model describing the model for the diagnostic imaging prescription. This draft is used in the HL7 Belgian workgroup for referral.

BeLaboratoryPrescription

Logical model describing the model for the prescription laboratory. This draft is used in the HL7 Belgian workgroup for laboratory.

BeModelNursingPrescription
BeModelReferralPrescription

Logical model describing the model for the prescription referral. This draft is used in the HL7 Belgian workgroup for referral.

BeModelReferralRequestGroup

Logical model describing the model for a group of referral prescriptions. This draft is used in the HL7 Belgian workgroup for referral.

BePhysiotherapyPrescription

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

BeAnnex81
BeLabPrescription

This is the Belgian profile for a laboratory order.

BeOrganizationTask

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

BePerformerTask

Subtask performed by one performer

BeReferralCarePlan
BeReferralCareServiceRequest
BeReferralPrescriptionDiagnosticImaging

Referral prescription for a generic diagnostic imaging. Please note in .orderDetail, a specific slicing is available to give guidance how to express acquisition modalities if needed. In future iterations of this profile, more slicing might provide additional guidance.

BeReferralPrescriptionNursing

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)

BeReferralRequestGroup

Envelope that allows different referralprescriptions to have an order

BeReferralServiceRequest

The common structure for referral prescription.

BeReferralTask

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

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

BeContainedOrLogicalReference

A reference limited to contained resources or resources with a logical identifier.

BeYearMonthDay

a datetime of length 10 or empty

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

BeCoPrescriber

Other practitioners that must take part in this prescripiton

BeCoPrescriberInfo

Info about the other practitioners that must take part in this prescripiton

BeContraindication

Contra indication in a prescription referral for diagnostic imaging.

BeContrastFluidUse

Whether the use of contrast fluid in diagnostic imaging can be defined as ‘If necessary’ or ‘Not permitted.’

BeFeedbackToPrescriber

Does the prescriber request feedback?

BeInformParty

Extra parties that need to be informed of the outcome, besides the prescriber.

BeLatestDraftDate

Request must leave draft status before

BeLatestEndDate

Request must be performed before

BePSSInfo

Information regarding the Prescription Search Support

BePerformerType

Types of performers that can execute this request

BeProposalType

Type of proposal

BeSupportingInfo

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.

BeUrgentCommunication

When there is a need to urgently communicate results of an order.

BeValidityPeriod

Begin and enddate of the validity of the request

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

BeCoPrescriptionStatus

This is the status of the prescription for the coprescriber

BeCommunicationMethod

Codes to define a communication method.

BeContrastFluidUse

Codes to define the use of contrast fluid.

BeReferralCategory

Codes to define the high level category for a referral prescription. SNOMED-CT codes in this valueset are just a draft proposal to give a general idea - pending an official valueset.

BeVSAnnex81ReasonCode

Nurse diagnostics and observations giving cause to the Annex 81

BeVSPerformerTaskStatusReason

Codes to explain the current status of a referral prescription.

BeVSPrescriptionStatusReason

This is the status reason of the prescription

BeVSRequestNoteType

Types of notes used in a referral prescription

BeVSRequestedServicesNurse

Codes indicating the requests that can be asked from a nurse.

BeVSRequestedServicesNurseDetail

Codes indicating the request details that can be asked from a nurse.

BeVSTreatmentStatusReason

Codes to explain the current status of a treatment in a referral prescription.

BeVsCoPrescriberChoice

Type of intended performer choice

BeVsProposalType

If the status of the request is proposal, this valueset indicates the different types of proposal

BeVsRequestIntent

The allowed intent codes in the context of referral prescription

Body Site

Body Site

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

BeCSCoPrescriberChoice

Type of intended performer choice

BeCommunicationCode

Communication codes in Belgium. To define a specific method of communicating. Initially defined as supporting CodeSystem for the referral prescription.

BeContrastFluidUse

Whether use of contrast fluid should be considered.

BePrescriptionProposalType

Prescription Proposal Type. Indicates the type of proposal (new or prolongation) as from the uses cases by NIHDI

BePrescriptionStatusReason

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

BeTempRequestedService

Temporary codes for indicating services that can be requested from a Nurse

BeTempRequestedServiceDetail

Temporary codes for indicating service details that can be requested from a Nurse

BeTreatmentStatusReason

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

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

BeNSCoronalertcode

Code as generated by the Coronalert app.

BeNSSpecimen

National identifier for a specimen when needed.

BeUnadressedHealthMessageExchangePlatform

UHMEP naming system

Terminology: Structure Maps

These define transformations to convert between data structures used by systems conforming to this implementation guide.

StructureMap/be-map-model-referral-prescription

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

Performer1
Requester1
condition1
dementia-condition
diagnostic-imaging-basic-example-concreteWithDetails
diagnostic-imaging-basic-example-concreteWithText
diagnostic-imaging-basic-example-everything-contained
diagnostic-imaging-basic-example-useOfModality
example01-care02-colon-cleansing
example01-care02-colon-cleansing-performer-task
example01-care02-colon-cleansing-referral-task
example02-referralprescription-nursing-digestive-system-care
example03-referralprescription-nursing-compressiontherapy
example04-referralprescription-nursing-bladder-care
example05-referralprescription-nursing-digestive-system-care
example06-referralprescription-nursing-compression-therapy
example09-referralprescription-nursing-woundcare
example12-referralprescription-nursing-annex81
example16-referralprescription-nursing-bladder-care
example24-referralprescription-nursing-non-reimbursable
example26-referralprescription-nursing-other
example32-referralprescription-nursing-chronical-psychiatric
gpvisit
laboratory-order-example1
patient1
performer-task
performer-task-1-uc2a-1
performer-task-1-uc5a-1
performer-task-2-uc2a-1
practitioner1
practitioner2
practitionerrole1
referral-task
referral-task-uc2a-1
referral-task-uc5a-1
referralprescription-nursing-example2-digestive-system-care
referralprescription-nursing-example3-compression-therapy
referralprescription-nursing-example5-digestive-system-care
referralprescription-nursing-example6-compression-therapy
requesterrole1
requesterrole2
terminology-expansion
uc2a
uc2a-1
uc2a-2
uc2a-3
uc5a-1
ucgh211-1
ucgh222p12-1
ucgh222p12-1-1
ucgh222p12-1-2
ucgh222p12-1-2-1
ucgh222p12-2
ucgh222p12-2-2
ucgh222p12-2-2-1
ucgh222p12-2-2-2
ucgh222p12-2-2-2-1
ucgh222p12-3
ucgh222p13
ucgh222p13-1
ucgh222p13-1-1
ucgh222p13-2
ucgh241p110-1
ucgh241p110-1-1
ucgh241p111-1
ucgh241p111-1-1
ucgh241p15-1
ucgh241p15-1-1
ucgh241p16-1
ucgh241p16-1-1
ucgh241p17-1
ucgh241p17-1-1
ucgh241p18-1
ucgh241p18-1-1
ucgh241p19-1
ucgh241p19-1-1