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: Appointment model

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

EHDS refined base model for Appointment. This is a simplified model with minimal information - it is not intended to cover the full functionality of booking systems.

Usages:

- Refer to this Logical Model: Encounter model

### Views of Logical Model

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

- Differential Table
- Snapshot Table

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSAppointment |  | 0..* | Base | Appointment model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | Appointment identifier
subject |  | 0..1 | EHDSPatient | The patient associated with the appointment.
status |  | 1..1 | CodeableConcept | The overall status of the Appointment. Binding Description: (preferred): HL7 Appointment status
class |  | 0..* | CodeableConcept | Classification of patient encounter (e.g. inpatient, outpatient, emergency). Binding Description: (preferred): HL7 Encounter class
serviceType |  | 0..* | CodeableConcept | The specific service that is to be performed during this appointment. Binding Description: (preferred): SNOMED CT
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that would be required to perform the service requested in this appointment Binding Description: (preferred): SNOMED CT
start |  | 0..1 | dateTime | Date and time that the appointment is to take place.
end |  | 0..1 | dateTime | Date and time that the appointment is to conclude.
note |  | 0..* | string | Additional notes/comments about the appointment.
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSAppointment.status | preferred |
EHDSAppointment.class | preferred |
EHDSAppointment.serviceType | preferred |
EHDSAppointment.specialty | preferred |

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSAppointment |  | 0..* | Base | Appointment model Instances of this logical model can be the target of a Reference
identifier |  | 0..* | Identifier | Appointment identifier
subject |  | 0..1 | EHDSPatient | The patient associated with the appointment.
status |  | 1..1 | CodeableConcept | The overall status of the Appointment. Binding Description: (preferred): HL7 Appointment status
class |  | 0..* | CodeableConcept | Classification of patient encounter (e.g. inpatient, outpatient, emergency). Binding Description: (preferred): HL7 Encounter class
serviceType |  | 0..* | CodeableConcept | The specific service that is to be performed during this appointment. Binding Description: (preferred): SNOMED CT
specialty |  | 0..* | CodeableConcept | The specialty of a practitioner that would be required to perform the service requested in this appointment Binding Description: (preferred): SNOMED CT
start |  | 0..1 | dateTime | Date and time that the appointment is to take place.
end |  | 0..1 | dateTime | Date and time that the appointment is to conclude.
note |  | 0..* | string | Additional notes/comments about the appointment.
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSAppointment.status | preferred |
EHDSAppointment.class | preferred |
EHDSAppointment.serviceType | preferred |
EHDSAppointment.specialty | preferred |

Other representations of model: CSV, Excel