Referral Prescription
1.0.0 - STU
Referral Prescription
1.0.0 - STU
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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| BeOpApproveAnnex81 |
Creates an approval from an Annex81 proposal |
| BeOpRejectAnnex81 |
Rejects an Annex81 proposal |
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 |
These define collections of interrelated resources that are useful to pass around as a group.
| BeGDFullReferralPrescription |
Specify to include all useful resources around a ServiceRequest that can be retrieved with the $graph operation. |
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| BeModelNursingPrescription | |
| BeModelReferralPrescription |
Logical model describing the model for the prescription referral. This draft is used in the HL7 Belgian workgroup for referral. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| BeAnnex81 | |
| BeOrganizationTask |
Subtask to assign the referral task and prescription to one or more members of this organisation |
| BePerformerTask |
Subtask performed by one performer |
| BeReferralServiceRequest |
The common structure for referral prescription. |
| BeReferralServiceRequestNursing |
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) |
| 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 |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| BeNoContainedReference |
A reference disallowing the use of contained references |
| BeYearMonthDay |
a datetime of length 10 or empty |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| BeLatestEndDate |
Request must be performed before |
| BePerformerType |
Types of performers that can execute this request |
| BeValidityPeriod |
Begin and enddate of the validity of the request |
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 |
| BeVSCoPrescriberChoice |
Type of intended performer choice |
| BeVSPerformerTaskStatusReason |
Codes to explain the current status of a referral prescription. |
| BeVSPrescriptionStatusReason |
This is the status reason of the prescription |
| 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 |
| 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. |
| BeVSTaskIntent |
The allowed intent codes in the context of tasks in the field of referral prescriptions |
| BeVSTreatmentStatusReason |
Codes to explain the current status of a treatment in a referral prescription. |
| Body Site |
Body Site |
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. |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| BeNsUhmepShort |
UHMEP userfriendly namingsystem |
| BeUnadressedHealthMessageExchangePlatform |
UHMEP naming system |
These define transformations to convert between data structures used by systems conforming to this implementation guide.
| StructureMap/be-map-model-referral-prescription |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
IG © 2022+ . Package hl7.fhir.be.referral#1.0.0 based on FHIR 4.0.1. Generated 2024-09-24
Links: Table of Contents |
QA Report |
Version History |
