MyHealth@EU Core - Downloaded Version 1.0.0 See the Directory of published versions

• Content
• Detailed Descriptions
• Mappings
• XML
• JSON
• TTL

Logical Model: Human name model

MyHealth@EU refined base model for Human name

Usages:

• Use this Logical Model: Health professional model, Patient model and Related person 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
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
use		0..1	CodeableConcept	Identifies the purpose of this name. Binding Description: (preferred): HL7 Name Use
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
prefix		0..*	string	Name parts that come before the name. Prefixes appear in the correct order for presenting the name.
suffix		0..*	string	Name parts that come after the name. Suffixes appear in the correct order for presenting the name.
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHumanName.​use	Base	preferred		Not State	Unknown

This structure is derived from EHDSHumanName

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
Documentation for this format

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
use		0..1	CodeableConcept	Identifies the purpose of this name. Binding Description: (preferred): HL7 Name Use
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
prefix		0..*	string	Name parts that come before the name. Prefixes appear in the correct order for presenting the name.
suffix		0..*	string	Name parts that come after the name. Suffixes appear in the correct order for presenting the name.
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHumanName.​use	Base	preferred		Not State	Unknown

This structure is derived from EHDSHumanName

Summary

Key Elements View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
use		0..1	CodeableConcept	Identifies the purpose of this name. Binding Description: (preferred): HL7 Name Use
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
prefix		0..*	string	Name parts that come before the name. Prefixes appear in the correct order for presenting the name.
suffix		0..*	string	Name parts that come after the name. Suffixes appear in the correct order for presenting the name.
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHumanName.​use	Base	preferred		Not State	Unknown

Differential View

This structure is derived from EHDSHumanName

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
Documentation for this format

Snapshot View

Name	Flags	Card.	Type	Description & Constraints    Filter: Bindings Constraints Obligations
MyHealthEuHumanName		0..*	EHDSHumanName	Human name model Elements defined in Ancestors:use, text, family, given, prefix, suffix
use		0..1	CodeableConcept	Identifies the purpose of this name. Binding Description: (preferred): HL7 Name Use
text	O	0..1	string	Specifies the entire name as it should be displayed e.g. on an application UI. Obligations Actor MAY:able-to-populate MyHealth@EU Handler
family	O	0..*	string	The family name/surname/last name of a person. Obligations Actor SHOULD:handle MyHealth@EU Handler
given	O	0..*	string	The given name/first name. Obligations Actor SHOULD:handle MyHealth@EU Handler
prefix		0..*	string	Name parts that come before the name. Prefixes appear in the correct order for presenting the name.
suffix		0..*	string	Name parts that come after the name. Suffixes appear in the correct order for presenting the name.
Documentation for this format

Terminology Bindings

Path	Status	Usage	ValueSet	Version	Source
MyHealthEuHumanName.​use	Base	preferred		Not State	Unknown

This structure is derived from EHDSHumanName

Summary

Other representations of profile: CSV, Excel