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

Home

Official URL: https://www.ehealth.fgov.be/standards/fhir/medication/ImplementationGuide/hl7.fhir.be.medication				Version: 1.1.0
Draft as of 2020-02-26				Computable Name: Medication

Use of MUST, SHOULD, MAY

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119:

1. MUST, or the terms “REQUIRED” or “SHALL”, mean that the definition is an absolute requirement of the specification.

2. MUST NOT, or the phrase “SHALL NOT”, mean that the definition is an absolute prohibition of the specification.

3. SHOULD, or the adjective “RECOMMENDED”, mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course.

4. SHOULD NOT, or the phrase “NOT RECOMMENDED” mean that there may exist valid reasons in particular circumstances when the particular behaviour is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behaviour described with this label.

5. MAY, or the adjective “OPTIONAL”, mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.)

Must Support

Unless otherwise stated, the following criteria apply to elements marked as “Must Support” in this Implementation Guide:

For technical profiles

Systems supporting the profile MUST NOT ignore the element.

• Systems receiving or consuming a resource instance:
  • MUST be able to process the element’s content when it is present
  • MUST process the content according to the rules defined for the profile
  • MUST NOT fail when the value is not present.
• Systems sending or creating a resource instance
  • SHOULD populate the element when the information is available
  • MUST populate the element according to the rules defined for the profile

For Logical Models

• Functional Analysis MUST consider the data element as defined
  • “Must Support” elements that are used in an implementation MUST inherit the behaviour and constraints defined for the data element
  • “Must Support” elements not needed in a particular implementation MAY be excluded from implementation but such exclusion MUST be described
• Derived implementations SHOULD inherit the field’s “Must Support” flag

Dependencies

This IG Contains the following dependencies on other IGs.

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.uv.extensions.r4#5.1.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, Apr 27, 2024 18:39+1000+10:00)

Package hl7.fhir.be.core#2.1.2 eHealth Platform Federal Core Profiles (built Fri, Aug 30, 2024 17:07+0200+02:00)

Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.be.medication.r4) and R4B (hl7.fhir.be.medication.r4b) are available.

Global Profiles

There are no Global profiles defined

Intellectual Property

This publication includes IP covered under the following statements.

• ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  • ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: BasedOnMedicationLine, BeDosage... Show 25 more, BeMedicationDispense, BeMedicationLine, BeMedicationPrescription, BeModelDosagingInformation, BeModelMedication, BeModelMedicationDispense, BeModelMedicationPrescription, BeModelMedicationType, BeModelMedicationTypeVS, BeNSCNK, BeNSCTIExtended, BeNSPrescriptions, BeNSProductPackage, DispenseRequestNeededCategory, DispenserTypes, ExposureCategory, InstructionsForReimbursement, Medication, MedicationExposureCategoryVS, MedicationLine, MedicationLineOrigintype, MedicationLineOrigintypeVS, MedicationRequestReimbursementType, MedicationRequestReimbursementTypeVS and OffLabel
• The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
  Show Usage
  • Unified Code for Units of Measure (UCUM): MedicationDispense/example-dispense-hospital
• This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  • SNOMED Clinical Terms® (SNOMED CT®): BeDosage, BeMedicationDispense, ExposureCategory, MedicationExposureCategoryVS and MedicationLine