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

Logical Model: EHDSHumanName - Detailed Descriptions

Draft as of 2025-06-13

Definitions for the EHDSHumanName logical model.

Guidance on how to interpret the contents of this table can be foundhere

0. EHDSHumanName
Definition

C.27 - EHDS refined base model for Human name


Base definition for all types defined in FHIR type system.

ShortHuman name modelBase for all types and resources
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition

Identifies the purpose for this name.

ShortC.27.1 - Use
Control0..1
Binding

hl7:NameUse

TypeCodeableConcept
4. EHDSHumanName.text
Definition

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

ShortC.27.2 - Text
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. EHDSHumanName.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortC.27.3 - Family
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. EHDSHumanName.given
Definition

The given name/first name (also known as forename or first name).

ShortC.27.4 - Given
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. EHDSHumanName.prefix
Definition

Name parts that come before the name. Prefixes appear in the correct order for presenting the name.

ShortC.27.5 - Prefix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. EHDSHumanName.suffix
Definition

Name parts that come after the name. Suffixes appear in the correct order for presenting the name.

ShortC.27.6 - Suffix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. EHDSHumanName
Definition

C.27 - EHDS refined base model for Human name

ShortHuman name model
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition

Identifies the purpose for this name.

ShortC.27.1 - Use
Control0..1
Binding

hl7:NameUse

TypeCodeableConcept
4. EHDSHumanName.text
Definition

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

ShortC.27.2 - Text
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. EHDSHumanName.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortC.27.3 - Family
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. EHDSHumanName.given
Definition

The given name/first name (also known as forename or first name).

ShortC.27.4 - Given
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. EHDSHumanName.prefix
Definition

Name parts that come before the name. Prefixes appear in the correct order for presenting the name.

ShortC.27.5 - Prefix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. EHDSHumanName.suffix
Definition

Name parts that come after the name. Suffixes appear in the correct order for presenting the name.

ShortC.27.6 - Suffix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension

Guidance on how to interpret the contents of this table can be foundhere

0. EHDSHumanName
Definition

C.27 - EHDS refined base model for Human name

ShortHuman name model
Control0..*
Is Modifierfalse
Logical ModelInstances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition

Identifies the purpose for this name.

ShortC.27.1 - Use
Control0..1
Binding

hl7:NameUse

TypeCodeableConcept
4. EHDSHumanName.text
Definition

Specifies the entire name as it should be displayed e.g. on an application UI. This may be provided instead of or as well as the specific parts.

ShortC.27.2 - Text
Control0..1
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
6. EHDSHumanName.family
Definition

The family name/surname/last name of the patient. This field can contain more than one element or multiple fields could be present.

ShortC.27.3 - Family
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
8. EHDSHumanName.given
Definition

The given name/first name (also known as forename or first name).

ShortC.27.4 - Given
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
10. EHDSHumanName.prefix
Definition

Name parts that come before the name. Prefixes appear in the correct order for presenting the name.

ShortC.27.5 - Prefix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension
12. EHDSHumanName.suffix
Definition

Name parts that come after the name. Suffixes appear in the correct order for presenting the name.

ShortC.27.6 - Suffix
Control0..*
Typestring
Primitive ValueThis primitive element may be present, or absent, or replaced by an extension