Summary
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
Table of Contents
- 0.1 EHDS Common Logical Models
- 0.2 EHDS ePrescription and eDispense Logical Models
- 0.3 EHDS Laboratory Domain Logical Models
- 0.4 EHDS Imaging Domain Logical Models
- 0.5 EHDS Hospital Discharge Report Domain Logical Models
- 0.6 EHDS Patient Summary Domain Logical Models
- 0.7 Structures: Logical Models
- 0.8 Structures: Data Type Profiles
0.1 EHDS Common Logical Models
Information Models for implementing EEHRxF services under EHDS. Format based on ISO 13972 “Health informatics — Clinical information models — Characteristics, structures and requirements.”
C.5 – EHDS refined base model for Address structure
C.22 – EHDS refined base model for Alert flag
C.21 – EHDS refined base model for Allergy Intolerance
C.20 – EHDS refined base model for Appointment
C.7 – 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.
D.1 – EHDS refined base model for Document attachments
C.19 – EHDS refined base model for Care plan
C.15 – 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.
C.31 – EHDS refined base model for Coverage
C.12 – EHDS refined base model for Device information
C.25 – EHDS refined base model for Device Use
C.30 – EHDS refined base model for Encounter
C.33 – EHDS refined base model for Endpoint
C.29 – EHDS refined base model for Episode of care
C.25 – EHDS refined base model for Functional status
C.XX – EHDS refined base model for Goal
C. – EHDS refined base model for Group
C.2 – EHDS refined base model for Health professional (HP)
C.27 – EHDS refined base model for Human name
C.24 – EHDS refined base model for Immunization
C.24 – EHDS refined base model for Immunization
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.
C.14 – EHDS refined base model for A photo, video, or audio recording acquired or used in healthcare.
C.18 – EHDS refined base model for Medication administration
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.
C.10 – EHDS refined base model for Observation information
C.1 – EHDS refined base model for Patient/subject information
C.3 – EHDS refined base model for Health provider or any other type of organization
C.16 – EHDS refined base model for An action that is or was performed on or for a patient
C.13 – EHDS refined base model for Patient/subject guardian and other related person information
EHDS refined base model for Report header data elements. Common for hospital discharge, laboratory and medical imaging reports.
C.8 – EHDS refined base model for Specification of requested service or services
C.XX – EHDS refined base model for Slot
C.9 – EHDS refined base model for Specimen information
C.28 – EHDS refined base model for Substance
C.20 – EHDS refined base model for Task
C.6 – EHDS refined base model for Telecommunication contact information structure
0.2 EHDS ePrescription and eDispense Logical Models
Information Models for implementing EEHRxF services for medication prescription and dispense services.
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).
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.
Logical model for medication dispensation (based on request or independently)
Logical model for medication prescription body. A prescription contains one or more prescription items.
0.3 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.”
C.11 – EHDS refined base model for Observation performed by laboratory
A – EHDS refined base model for Laboratory order
B.1 – EHDS refined base model for Laboratory order body
A.1 – EHDS refined base model for Laboratory order header data elements
B.1 – EEHRxF refined base model for Laboratory result report body
A.1 – EHDS refined base model for laboratory report header data elements
A – EHDS refined base model for Laboratory result report
0.4 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.”
B.1 – EHDS refined base model for Imaging report body
A.1 – EHDS refined base model for Imaging ReportAn imaging report reflects the observations and interpretations of one or more imaging studies. It usually contains elements such as the reason why the study is requested, relevant contextual medical information, the used modality and its settings, procedures and body localisations that were used, a description of the observations and findings, exposure information, conclusion and advice. Definition Source eHealth Network Read More header data elements
A – EHDS refined base model for Imaging Result Report
C.32 – EHDS refined base model for Imaging study
0.5 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.”
A – EHDS refined base model for Hospital Discharge Report
A.1 – EHDS refined base model for Hospital Discharge Report header data elements
C.23 – EHDS refined base model for Inpatient encounter
0.6 EHDS Patient Summary 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.”
B.1 – EHDS refined base model for Patient SummaryHealth record extract comprising a standardized collection of clinical and contextual information (retrospective, concurrent, prospective) that provides a snapshot in time of a subject of care’s health information and healthcare. is an identifiable dataset of essential and understandable health information that includes the most important clinical facts required to ensure safe and secure healthcare. This summarised version of the patient’s Read More body data elements
A.1 – EHDS refined base model for Patient Summary header data elements
A – EHDS refined base model for Patient Summary Report
0.7 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.
C.34 – EHDS refined base model for Clinical impression
EHDS refined base model for document header data elements, including the common header for all resources. Data relevant to document type and its content for administrative and searching purposes.
MetadataInformation that is given to describe or help you use other information. Metadata are information parameters that provide contextual information about the actual information within a document (or other information container). Examples are: date of event and/or publication, size in bytes, technical format, template, standard version, document version, author specialty, functional category et cetera. Definition Source Guideline on the electronic Read More elements for a header of medication dispense or dispense decline.
Logical model for medication prescription header.
Common header elements for all documents and their independently functioning parts, e.g FHIR resources.
0.8 Structures: Data Type Profiles
These define constraints on FHIR data types for systems conforming to this implementation guide.