Human name model - Definitions - HL7 Europe Base and Core FHIR IG v0.1.0-snapshot

HL7 Europe Base and Core FHIR IG
0.1.0-snapshot - draft 150

This page is part of the HL7 Europe Base and Core (v0.1.0-snapshot: QA Preview) based on FHIR (HL7® FHIR® Standard) v5.0.0. This version is a pre-release. The current official version is 0.1.0-ballot. For a full list of available versions, see the Directory of published versions

Logical Model: EHDSHumanName - Detailed Descriptions

Draft as of 2025-09-23

Definitions for the EHDSHumanName logical model.

Key Elements Table
Differential Elements Table
Snapshot Elements Table

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

0. EHDSHumanName
Definition	EHDS refined base model for Human name Base definition for all types defined in FHIR type system.
Short	Human name modelBase for all types and resources
Control	0..*
Is Modifier	false
Logical Model	Instances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition	Identifies the purpose for this name.
Short	Use
Control	0..1
Binding	hl7:NameUse
Type	CodeableConcept
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.
Short	Text
Control	0..1
Type	string
Primitive Value	This 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.
Short	Family
Control	0..*
Type	string
Primitive Value	This 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).
Short	Given
Control	0..*
Type	string
Primitive Value	This 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.
Short	Prefix
Control	0..*
Type	string
Primitive Value	This 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.
Short	Suffix
Control	0..*
Type	string
Primitive Value	This 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	EHDS refined base model for Human name
Short	Human name model
Logical Model	Instances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition	Identifies the purpose for this name.
Short	Use
Control	0..1
Binding	hl7:NameUse
Type	CodeableConcept
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.
Short	Text
Control	0..1
Type	string
Primitive Value	This 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.
Short	Family
Control	0..*
Type	string
Primitive Value	This 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).
Short	Given
Control	0..*
Type	string
Primitive Value	This 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.
Short	Prefix
Control	0..*
Type	string
Primitive Value	This 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.
Short	Suffix
Control	0..*
Type	string
Primitive Value	This 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	EHDS refined base model for Human name
Short	Human name model
Control	0..*
Is Modifier	false
Logical Model	Instances of this logical model are not marked to be the target of a Reference
2. EHDSHumanName.use
Definition	Identifies the purpose for this name.
Short	Use
Control	0..1
Binding	hl7:NameUse
Type	CodeableConcept
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.
Short	Text
Control	0..1
Type	string
Primitive Value	This 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.
Short	Family
Control	0..*
Type	string
Primitive Value	This 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).
Short	Given
Control	0..*
Type	string
Primitive Value	This 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.
Short	Prefix
Control	0..*
Type	string
Primitive Value	This 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.
Short	Suffix
Control	0..*
Type	string
Primitive Value	This primitive element may be present, or absent, or replaced by an extension

Links: Table of Contents | QA Report

Propose a change external