Medication
1.1.0 - STU

Medication, published by eHealth Platform. 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/ 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.

### Logical Data Models

Logical data models. The Logical data models are representations of the data needs for the scope of this Implementation Guide. The data models are primarily aligned with key projects, namely VIDIS, but are prepared in coordination with the Belgian community to ensure a common data structure that supports the projects and the implementation data needs.

Dosaging (model) | Structured Dosage data model.
Medication (model) | Logical data model for medication.
Medication Dispense (model) | This is the logical model for the Dispense Record entry - the information that can be captured upon the act of dispensing - in a hospital pharmacy, or a community pharmacy. This is not for a future dispense, rather a record of an actual dispense.
Medication Line (model) | Logical data model for medication line.
Medication prescription (model) | Logical model for medication prescription (or some other form of order)

### Profiles

Profiles for Medication. These are implementable FHIR profiles.

BeMedicationDispense | Defines constraints and extensions on the Medication Dispense resource for a record of a dispensation in Belgium.
BeMedicationLine | Medication Line profile - contains the overview information for a single medication item
BeMedicationPrescription | Medication Request profile - The common structure for medication request
Medication Dosage | Specifications for a medication dosage for use in Belgian profiles.

### Extensions

Extensions for FHIR resources, to be used in Profiles

BasedOnMedicationLine | Based on medication line.
BeExtAdherenceStatus | Medication Line Adherence Status - statuses of taking the medication.
BeExtInstructionsForReimbursement | Instructions for Reimbursement.
BeExtMedicationType | The type of medication.
BeExtRecordedDate | The date the information was recorded
BeExtRecorder | The person that recorded the information
BeMedicationExposureCategory | Exposure - category.
Medication Line Registration Status | This extension indicates the registration status of a medication line, such as whether it is draft, recorded, or entered-in-error.
MedicationRequest - Off-label use | Indicates that the order placer has knowingly prescribed the medication for an indication, age group, dosage, or route of administration that is not approved by the regulatory agencies and is not mentioned in the prescribing information for the product.

### Terminology

Terminology for Medication. These are value sets, code systems and naming systems for identifiers.

Adherence Status Reason | Reasons for non-adherence to a treatment or intervention.
Adherence Status Reason ValueSet | ValueSet containing reasons for non-adherence to a treatment or intervention.
be-ns-cnk-codes | Naming System - CNK Product Codes
be-ns-cti-extended-code | Naming System - CTI Extended Codes
be-ns-prescription-ids | Naming System - Prescription IDs
be-ns-product-package-type | Naming System - Prescription IDs
BeExtAdherenceStatus | The status of taking the medication.
Dispenser Types | Dispenser Types - from hcparty
Medication exposure intent | The exposure purpose of a medication - whether the medication is given for therapeutic or prophylactic purposes.
Medication Line Adherence Status | Medication Line Adherence Status - ValueSet.
Medication Line Registration Status | This code system defines the registration statuses for medication lines.
Medication Line Registration Status Value Set | This value set includes the registration statuses for medication lines.
Medication origin Type | Medication origin type
Medication origin type value set | Medication origin type value set
Medication preparation Type | Medication preparation type
Medication preparation Type value set | Medication preparation type value set
Medication Prescription Status | Medication prescription status codes.
Medication request reimbursement type | Medication request reimbursement type - instructions for reimbursement of the medication request
Medication request reimbursement type ValueSet | Medication request reimbursement type - instructions for reimbursement of the medication request
Route of Administration ValueSet | This ValueSet contains codes for the route of administration of medications. It is used to specify how a medication is administered to a patient, such as orally, intravenously, or topically.

### Example: Example Instances

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

Example Dispense (minimal) | Dispense Example - Minimal amount of information
Example Dispense (simple) | Dispense Example - Simple example of a dispense
Example Dispense entry - Community Pharmacy dispense, from prescription, with contained org. | Medication Dispense example
Example Dispense from a hospital pharmacy | A dispense from a hospital pharmacy, with a hospital nihdi and based on a prescription
Medication Dispense example | Dispense entry Example - Community Pharmacy dispense, from prescription
Prescription Example 01 - Lasix | Lasix 50 x 40 mg - Every other day (QOD)
Prescription Example 02 - Hukyndra | Hukyndra 6 x 40mg/0.4ml - Loading dose: week 0: 80mg, week 2: 40mg, then 40mg every 2 weeks
Prescription Example 03 - Bisoprolol (VOS) | Bisoprolol tablets 2.5 mg - 1 x / day 2.5 mg for 3 months (VOS - Voorschrift Op Stofnaam)
Prescription Example 04 - Gutron (Import) | Gutron 5mg - Dose escalation: 2.5mg 3x/day for 1 week, then increase weekly by 2.5mg to 10mg 3x/day maintenance
apotheek-onder-de-toren | Example organization for a pharmacy