ARCHETYPE Structured name of a person (openEHR-EHR-CLUSTER.structured_name.v1)

ARCHETYPE IDopenEHR-EHR-CLUSTER.structured_name.v1
ConceptStructured name of a person
DescriptionDiscrete components of an individual's name.
UseUse to record details about the structured name of an individual as they are known or understood in the course of clinical documentation, often ad hoc or when it is not appropriate or possible to use a formal demographic register or index. In most simple clinical recording use cases, the unstructured 'Name' element within the CLUSTER.person archetype will be sufficient to record the name of an individual as part of a health record. However, in circumstances where a structured name is necessary or desirable for clinical recording purposes, nest this archetype within the 'Structured name' SLOT in CLUSTER.person archetype. Each data element can be entered as a string of free text - for example, 'Prof Dr', 'Sonja Jane', 'Smith-Brown', 'MP'. Alternatively, as each data element is repeatable within a template: - 'Title' could be cloned to 'Title 1' for the value 'Prof' and 'Title 2' for the value 'Dr'; and - 'Given name' could be cloned and renamed to 'First name' for the value 'Sonja' and 'Middle name' for the value 'Jane'. While this archetype has been aligned with ISO 22220, preferred name, name usage, valid dates and the repeating Name component/Order grouping has intentionally not been replicated due to the reduced scope of this archetype. It is anticipated that in most use cases for which this archetype has been designed, complex family names will simply be recorded as a string. However, it is possible to record them with more granularity and within this structured name pattern using guidance and examples from ISO 22220:2007 (Annex F), including: - Family name first, given name/s last; - Family names with prefixes eg El Haddad or van der Heyden; and - Names containing both father's and mother's family names.
MisuseNot to be used if an unstructured text string representing the individual's name is adequate for the purpose. Use the 'Name' data element within the CLUSTER.person for this purpose. Not to be used for complex name representation or management, such as preferred names, name usage or valid dates of usage. Use a formal Master Patient Index or Health Provider Index for this purpose, or archetypes based on the openEHR Demographic Information Model. Not to be used to represent or replace formal identification management or for the purposes of maintaining an official demographic register or index. Use a formal Master Patient Index or Health Provider Index for this purpose, or archetypes based on the openEHR Demographic Information Model. Not to be used to represent the subject of care, participants or author of the record and similar data elements that should be represented formally in the health record using the Reference Model attributes.
PurposeTo record details about the structured name of an individual as they are known or understood in the course of clinical documentation.
ReferencesHealth Care Client Identification - AS 5017-2006. New South Wales (AU): Standards Australia; 2006.

Health Care Provider Identification - AS 4846-2006. New South Wales (AU): Standards Australia; 2006.

Health informatics — Identification of subjects of health care - ISO/TS 22220:2007. Geneva: International Organization for Standardization; 2007.

HL7 FHIR Resource - Person v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/person.html.
Copyright© openEHR Foundation
AuthorsAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-04-14
Other Details LanguageAuthor name: Heather Leslie
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-04-14
OtherDetails Language Independent{licence=This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/., custodian_organisation=openEHR Foundation, references=Health Care Client Identification - AS 5017-2006. New South Wales (AU): Standards Australia; 2006. Health Care Provider Identification - AS 4846-2006. New South Wales (AU): Standards Australia; 2006. Health informatics — Identification of subjects of health care - ISO/TS 22220:2007. Geneva: International Organization for Standardization; 2007. HL7 FHIR Resource - Person v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/person.html., original_namespace=org.openehr, original_publisher=openEHR Foundation, custodian_namespace=org.openehr, MD5-CAM-1.0.1=4C91B974D7EE4B40B0579711D6B62439, build_uid=efeed73f-bc3f-4b27-a1f9-f2ac5d082e4a, revision=1.0.1}
Keywordsperson, individual, name
Lifecyclepublished
UIDc4ed12e0-471f-40ec-b70d-be07ef3c5932
Language useden
Citeable Identifier1013.1.5359
Revision Number1.0.1
AllArchetype [runtimeNameConstraintForConceptName=null, archetypeConceptBinding=null, archetypeConceptDescription=Discrete components of an individual's name., archetypeConceptComment=null, otherContributors=Dag Aarhus, Vestre Viken HF, Norway
Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)
Keisha Barwise, MOHW/IDB HSSP Project, Jamaica
SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India
Terje Bless, Helse Nord FRESK, Norway
Yexuan Cheng, 浙江大学, China
Candice de Lisser, Ministry of Health and Wellness, Jamaica
Ludvig Eek Hofmann, Cambio Healthcare Systems AB, Sweden
Alexander Eikrem-Lüthi, Lovisenberg Diakonale Sykehus, Norway
Valborg Ellingsen, Haraldsplass Diakonale sykehus, Norway
Heather Grain, Llewelyn Grain Informatics, Australia
Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (openEHR Editor)
Rebecka Hansson, Cambio Healthcare Systems AB, Sweden
Roar Holm, Helse Vest IKT A/S, Norway
Joost Holslag, Nedap, Netherlands
Evelyn Hovenga, EJSH Consulting, Australia
Gunnar Jårvik, Helse Vest IKT AS, Norway
Gunn-Lisbeth Kleiven, Oslo universitetssykehus HF, Norway
Shinji Kobayashi, National Institute of Public Health, Japan
Kanika Kuwelker, Helse Vest IKT, Norway
Jörgen Kuylenstierna, eWeave AB, Sweden
Liv Laugen, ​Oslo University Hospital, Norway, Norway (openEHR Editor)
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Mikael Nyström, Cambio Healthcare Systems AB, Sweden
Erik Skjemstad, Helse Nord RHF, Norway
Natalia Strauch, Medizinische Hochschule Hannover, Germany
Norwegian Review Summary, Norwegian Public Hospitals, Norway
Nyree Taylor, Ocean Health Systems, Australia
Anders Thurin, VGR, Sweden
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor), originalLanguage=en, translators=German: Natalia Strauch, Alina Rehberg, Medizinische Hochschule Hannover, Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de
Norwegian Bokmål: John Tore Valand, Vebjørn Arntzen, Kanika Kuwelker, Marit Alice Venheim, Helse Vest IKT AS, Helse Bergen, Oslo University Hospital, john.tore.valand@helse-vest-ikt.no, varntzen@ous-hf.no, kanika.kuwelker@helse-vest-ikt.no, marit.alice.venheim@helse-vest-ikt.no
, subjectOfData=unconstrained, archetypeTranslationTree=null, topLevelToAshis={other_participations=[], provider=[], ism_transition=[], events=[], items=[ResourceSimplifiedHierarchyItem [path=/items[at0001], code=at0001, itemType=ELEMENT, level=1, text=Title, description=One or more honorific form(s) of address commencing a name., comment=Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0002], code=at0002, itemType=ELEMENT, level=1, text=Given name, description=One or more unique name(s) used to identify an individual within a family group., comment=Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0005], code=at0005, itemType=ELEMENT, level=1, text=Family name, description=One or more name(s) that an individual has in common with a family group., comment=Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0006], code=at0006, itemType=ELEMENT, level=1, text=Suffix, description=One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components., comment=Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null]], capabilities=[], data=[], activities=[], context=[], target=[], relationships=[], details=[], protocol=[], identities=[], description=[], content=[], source=[], state=[], contacts=[], credentials=[]}, topLevelItems={items=ResourceSimplifiedHierarchyItem [path=ROOT_/, code=at0000, itemType=CLUSTER, level=0, text=null, description=null, comment=null, uncommonOntologyItems=null, occurencesFormal=1..1, occurencesText=Mandatory, cardinalityFormal=1..*, cardinalityText=, subCardinalityFormal=null, subCardinalityText=null, dataType=CLUSTER, bindings=null, values=null, extendedValues=null]}, addHierarchyItemsTo=items, currentHierarchyItemsForAdding=[ResourceSimplifiedHierarchyItem [path=/items[at0001], code=at0001, itemType=ELEMENT, level=1, text=Title, description=One or more honorific form(s) of address commencing a name., comment=Occurrences for this data element are set to 0..* to allow for more than one Title to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Doctor'; 'Ms'; 'Mx'; or 'Professor Dr'., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0002], code=at0002, itemType=ELEMENT, level=1, text=Given name, description=One or more unique name(s) used to identify an individual within a family group., comment=Occurrences for this data element are set to 0..* to allow for more than one Given name to be recorded. In addition, this data element may be cloned and renamed within a template to allow discrete recording of different types of Given name - for example 'First name', 'Middle name', 'Preferred name' or 'Nickname', as required for a specific use case., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0005], code=at0005, itemType=ELEMENT, level=1, text=Family name, description=One or more name(s) that an individual has in common with a family group., comment=Also known as 'Last name' or 'Surname'. Occurrences for this data element are set to 0..* to allow for more than one Family name to be recorded. Complex names such as 'El Haddad' or 'van der Heyden' can be recorded using this naming pattern, as identified in ISO 22220 (Annex F), but for the intended use case for this archetype it is most likely that the full family name will be recorded as a string., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null], ResourceSimplifiedHierarchyItem [path=/items[at0006], code=at0006, itemType=ELEMENT, level=1, text=Suffix, description=One or more term(s) placed after all other name components, usually to differentiate an individual from a family member with identical Given and Family name components., comment=Occurrences for this data element are set to 0..* to allow for more than one Suffix to be recorded. Coding with an external terminology is preferred, where possible. For example: 'Junior (Jr)'; 'Senior (Sr)'; 'Second (II)'., uncommonOntologyItems=null, occurencesFormal=0..*, occurencesText=Optional, repeating, cardinalityFormal=null, cardinalityText=null, subCardinalityFormal=null, subCardinalityText=null, dataType=DV_TEXT, bindings=null, values=, extendedValues=null]], minIndents={}, termBindingRetrievalErrorMessage=null]