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-D7-3 and changes regularly. See the Directory of published versions

## Logical Model: Patient model

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

EHDS refined base model for patient (subject of care) information

Usages:

- Use this Logical Model: Advance directive model, Appointment model, Coverage model, DataSet model... Show 11 more, Device use model, Discharge Report model, Imaging report model, Laboratory order body model, Laboratory order header model, Laboratory report body model, Laboratory report header model, Medication dispense model, Observation model, Related person model and Specimen model
- Refer to this Logical Model: Laboratory order header model and Media model

You can also check for usages in the FHIR IG Statistics

### Formal Views of Profile Content

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

- Key Elements Table
- Differential Table
- Snapshot Table
- Statistics/References
- All

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

This structure is derived from Base

Summary

Mandatory: 0 element(1 nested mandatory element)

Key Elements View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

Differential View

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

Snapshot View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSPatient |  | 0..* | Base | Patient model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 1..* | Identifier | An identifier of the patient that is unique within a defined scope (typically a national patient identifier, but it can also be a temporary identifier issued by the EHR).
name |  | 0..* | EHDSHumanName | Name associated with the patient/subject.
dateOfBirth |  | 0..1 | dateTime | Date of birth
administrativeGender |  | 0..1 | CodeableConcept | Administrative gender Binding Description: (preferred): HL7 Administrative Gender
address |  | 0..* | EHDSAddress | Mailing and home or office addresses.
telecom |  | 0..* | EHDSTelecom | Telecommunication contact information (addresses) associated to a person.
maritalStatus |  | 0..1 | CodeableConcept | Marital (civil) status of a patient Binding Description: (preferred): HL7 marital-status
communicationLanguage |  | 0..* | CodeableConcept | The language which can be used to communicate with the patient about his or her health. Binding Description: (preferred): BCP 47
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSPatient.administrativeGender | preferred |
EHDSPatient.maritalStatus | preferred |
EHDSPatient.communicationLanguage | preferred |

This structure is derived from Base

Summary

Mandatory: 0 element(1 nested mandatory element)

Other representations of profile: CSV, Excel