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: Related person model

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

EHDS refined base model for Patient/subject guardian and other related person information

Usages:

- Use this Logical Model: Advance directive model, Device use model, Discharge Report model, Imaging report model... Show 2 more, Laboratory report header model and Medication dispense model
- Refer to this Logical Model: Laboratory order header 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
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | preferred |

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | preferred |

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | 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
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | preferred |

Differential View

This structure is derived from Base

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings (Differential)

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | preferred |

Snapshot View

Name | Flags | Card. | Type | Description & Constraints Filter: Bindings Constraints Obligations
--- | --- | --- | --- | ---
EHDSRelatedPerson |  | 0..* | Base | Related person model Instances of this logical model can be the target of a Reference
personalIdentifier |  | 0..* | Identifier | Personal identifier
name |  | 0..* | EHDSHumanName | Name
subject |  | 1..1 | EHDSPatient | The patient in relation to whom the related person is defined.
relationship |  | 0..1 | CodeableConcept | Relationship Binding Description: (preferred): HL7 RoleCode
address |  | 0..* | EHDSAddress | Address
telecom |  | 0..* | EHDSTelecom | Telecom
Documentation for this format

#### Terminology Bindings

Path | Conformance | ValueSet | URI
EHDSRelatedPerson.relationship | preferred |

This structure is derived from Base

Summary

Mandatory: 0 element(1 nested mandatory element)

Other representations of profile: CSV, Excel