EHDS Logical Information Models
0.1.0 - ci-build

EHDS Logical Information Models, published by Xt-EHR. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Xt-EHR/xt-ehr-common/tree/stakeholder-consultation-D6-1 and changes regularly. See the Directory of published versions

## Logical Model: Medication Statement

Official URL: https://www.xt-ehr.eu/specifications/fhir/StructureDefinition/EHDSMedicationStatement | Version: 0.1.0
Draft as of 2025-07-08 | Computable Name: EHDSMedicationStatement

Statement about a single medication as part of a medication summary.

Medication summary is suggested as a mandatory section of Patient Summary. Implementers should as a minimum be able to produce a list of medication. If the producing system have no record of medication to list (e.g. the patient uses no medication, or the system have no medication information), it must provide a reason. This is similar to the other mandatory sections, and in accordance with the specification in ISO IPS and updates to the HL7 FHIR IPS. There are several required elements for each listed medication, as both type of medication, its dose and instructions for use is needed for safe communication. The Patient Summary is however meant as a summery, and it is not necessary to include all the same information elements that are needed for ePrescription and eDispensation. We welcome feedback on needed elements, and potential consequences of omitting or including requirements for certain elements. This is similar to the other mandatory sections, and in accordance with the specification in ISO IPS and updates to the HL7 FHIR IPS.

Receiving systems must be able to handle the data and are encouraged to display the received information to the user but are not obliged to do so.

The information elements and value sets suggested is taken from eHN GL, MyHealth@EU and HL7 FHIR IPS.

Feedback is welcome on any aspect of the content.
However, the following topics have been identified as areas where input would be particularly valuable:

- intendedUseType - used as a category of purpose of use, or simply to signal whether a medication is used for therapeutic, diagnosis, prophylaxis, etc.

Usages:

- Use this Logical Model: Patient summary model

### Views of Logical Model

Description of Differentials, Snapshots and how the different presentations work.

- Differential Table
- Snapshot Table

This structure is derived from EHDSDataSet

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSMedicationStatement |  | 0..* | EHDSDataSet | Elements defined in Ancestors:header, presentedForm Medication Statement Instances of this logical model can be the target of a Reference
medicationTreatmentStatus |  | 0..1 | CodeableConcept | The current status of the taking of medicine
medication |  | 1..1 | EHDSMedication | Describes the medicinal product.
medicationReason |  | 0..* | CodeableConcept | Coded reason for the use of the medication (typically diagnosis, or a procedure)
medicationReasonText |  | 0..1 | string | Reason for the use of the medication (typically diagnosis, or a procedure) in free text.
intendedUseType |  | 0..1 | CodeableConcept | The type of intended use of the medication, e.g. prophylactic, therapeutic, diagnostic, anesthesia, etc.
dosageInstructions |  | 1..* | EHDSDosaging | Details of how medication is/was taken or should be taken
periodOfUse |  | 0..1 | Period | Period when patient took, is taking or is expected to take the medication
Documentation for this format

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSMedicationStatement |  | 0..* | EHDSDataSet | Elements defined in Ancestors:header, presentedForm Medication Statement Instances of this logical model can be the target of a Reference
header |  | 1..1 | Base | Common header for all patient-related data
subject |  | 1..1 | EHDSPatient | Subject
identifier |  | 0..* | Identifier | Business identifier for the object
authorship |  | 1..* | Base | Authorship
author[x] |  | 1..1 |  | Author
authorEHDSHealthProfessional |  |  | EHDSHealthProfessional |
authorEHDSOrganisation |  |  | EHDSOrganisation |
authorEHDSDevice |  |  | EHDSDevice |
datetime |  | 1..1 | dateTime | Date and time of authoring/issuing
lastUpdate |  | 0..1 | dateTime | Date and time of the last update to the resource
status |  | 1..1 | CodeableConcept | Status of the resource
statusReason[x] |  | 0..1 |  | Reason for the current status of the resource.
statusReasonCodeableConcept |  |  | CodeableConcept |
statusReasonString |  |  | string |
language |  | 0..1 | CodeableConcept | Language Binding Description: (preferred): BCP 47
version |  | 0..1 | string | Version
presentedForm |  | 0..* | EHDSAttachment | A narrative easy-to-read representation of the full data set, e.g. PDF-version of a document
medicationTreatmentStatus |  | 0..1 | CodeableConcept | The current status of the taking of medicine
medication |  | 1..1 | EHDSMedication | Describes the medicinal product.
medicationReason |  | 0..* | CodeableConcept | Coded reason for the use of the medication (typically diagnosis, or a procedure)
medicationReasonText |  | 0..1 | string | Reason for the use of the medication (typically diagnosis, or a procedure) in free text.
intendedUseType |  | 0..1 | CodeableConcept | The type of intended use of the medication, e.g. prophylactic, therapeutic, diagnostic, anesthesia, etc.
dosageInstructions |  | 1..* | EHDSDosaging | Details of how medication is/was taken or should be taken
periodOfUse |  | 0..1 | Period | Period when patient took, is taking or is expected to take the medication
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSMedicationStatement.header.language | preferred |

Other representations of model: CSV, Excel