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-2 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.

### EHDS Patient Summary Logical Models

Information Models for implementing EEHRxF Patient Summary under EHDS. Format based on ISO 13972 "Health informatics — Clinical information models — Characteristics, structures and requirements."

Patient summary model | EHDS refined base model for Patient Summary

### EHDS ePrescription and eDispense Logical Models

Information Models for implementing EEHRxF services for medication prescription and dispense services.

Medication dispense decline model | Explicit statement about declining the dispense request (prescription), usually recorded in order to communicate the issue back to the prescriber. Reasons for declining a dispense may vary, but typically this statement is only sent when a following action is expected on the prescriber’s side (cancelling or changing the problematic prescription or the whole treatment).
Medication dispense model | Logical model for medication dispensation (based on request or independently)
Medication prescription model | Logical model for medication prescription. A prescription contains one or more prescription items.

### EHDS Laboratory Domain Logical Models

Information Models for implementing EEHRxF services in the laboratory domain under EHDS. Format based on ISO 13972 "Health informatics — Clinical information models — Characteristics, structures and requirements."

Laboratory observation model | C.11 - EHDS refined base model for Observation performed by laboratory
Laboratory order | A - EHDS refined base model for Laboratory order
Laboratory order body model | B.1 - EHDS refined base model for Laboratory order body
Laboratory order header model | A.1 - EHDS refined base model for Laboratory order header data elements
Laboratory report body model | B.1 - EEHRxF refined base model for Laboratory result report body
Laboratory report header model | A.1 - EHDS refined base model for laboratory report header data elements
Laboratory report model | A - EHDS refined base model for Laboratory result report

### EHDS Imaging Domain Logical Models

Information Models for implementing EEHRxF services in the imaging domain under EHDS. Format based on ISO 13972 "Health informatics — Clinical information models — Characteristics, structures and requirements."

Imaging report body model | B.1 - EHDS refined base model for Imaging report body
Imaging report header model | A.1 - EHDS refined base model for Imaging Report header data elements
Imaging report model | A - EHDS refined base model for Imaging Result Report
Imaging study model | C.32 - EHDS refined base model for Imaging study

### EHDS Hospital Discharge Report Domain Logical Models

Information Models for implementing EEHRxF Hospital discharge report under EHDS. Format based on ISO 13972 "Health informatics — Clinical information models — Characteristics, structures and requirements."

Condition HDR model | C.38 - EHDS refined base model for Condition HDR
Hospital Discharge Report body model | EHDS refined base model for Hospital Discharge Report body
Hospital Discharge Report header model | A.1 - EHDS refined base model for Hospital Discharge Report header data elements
Hospital Discharge Report model | A - EHDS refined base model for Hospital Discharge Report
Inpatient encounter model | C.23 - EHDS refined base model for Inpatient encounter

### Structures: Logical Models

These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.

Address model | EHDS refined base model for Address structure
Alert flag model | C.22 - EHDS refined base model for Alert flag
Allergy intolerance model | EHDS refined base model for allergy/intolerance
Appointment model | 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.
Attachment model | EHDS refined base model for This type is for containing or referencing attachments - additional data content defined in other formats. The most common use of this type is to include images or reports in some report format such as PDF. However, it can be used for any data that has a MIME type.
Body structure model | EHDS refined base model for Body structure
Care plan model | EHDS simplified model for care plan. The model includes very minimal information and is not designed to cover the full functionality of care plans.
Condition model | EHDS refined base model for A clinical condition, problem, diagnosis, or other event, situation, issue, or clinical concept that has risen to a level of concern.
Coverage model | EHDS refined base model for Coverage
DataSet model | Common elements (including header) for all documents and their independently functioning parts, e.g FHIR resources.
Device model | EHDS refined base model for Device information
Device use model | EHDS refined base model for Device Use
Document model | EHDS refined base model for common document data elements, including the common header. Data relevant to document type and its content for administrative and searching purposes.
Dosage model | C.40 - EHDS refined base model for Dosage
Dosaging model | Logical model for usage instructions for administring the requested product. Based on FHIR Dosage complex data type. When implemented, this model may be reduced significantly according to the specific use case.
Encounter model | C.30 - EHDS refined base model for Encounter
Endpoint model | C.33 - EHDS refined base model for Endpoint
Episode of care model | C.29 - EHDS refined base model for Episode of care
Family member history model | C.37 - EHDS refined base model for Family member history
Functional status | EHDS refined base model for Functional status
Group model | C. - EHDS refined base model for Group
Health professional model | EHDS refined base model for Health professional (HP)
Human name model | C.27 - EHDS refined base model for Human name
Immunization model | C.24 - EHDS refined base model for Immunization
Location model | C.17 - EHDS refined base model for Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.
Media model | C.14 - EHDS refined base model for A photo, video, or audio recording acquired or used in healthcare.
Medication administration model | EHDS refined base model for medication administration
Medication statement model | C.39 - EHDS refined base model for Medication statement
Medicinal product model | Logical model for prescribed/dispensed medication. The model is shared by statements, requests, dispensations, and treatment lines. Each of those may have different restrictions in FHIR profile.
Observation model | C.10 - EHDS refined base model for Observation information
Organization model | C.3 - EHDS refined base model for Health provider or any other type of organization
Patient model | C.1 - EHDS refined base model for Patient/subject information
Procedure model | C.16 - EHDS refined base model for An action that is or was performed on or for a patient
Related person model | C.13 - EHDS refined base model for Patient/subject guardian and other related person information
Service request model | C.8 - EHDS refined base model for Specification of requested service or services
Specimen model | C.9 - EHDS refined base model for A sample to be used for Analysis
Substance model | C.28 - EHDS refined base model for Substance
Telecom model | C.6 - EHDS refined base model for Telecommunication contact information structure

### Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

ANY | An abstract type
Coded | Coded data element