Modellbiblioteket openEHR Fork
Name
Structured name of a person
Description
Discrete components of an individual's name.
Keywords
person
individual
name
Purpose
To record details about the structured name of an individual as they are known or understood in the course of clinical documentation.
Use
Use 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.
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.
Misuse
Not 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.
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.
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.
Archetype Id
openEHR-EHR-CLUSTER.structured_name.v1
Copyright
© openEHR Foundation
Licencing
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/.
Original Author
Heather Leslie
Atomica Informatics
Atomica Informatics
Date Originally Authored
To record details about the structured name of an individual as they are known or understood in the course of clinical documentation.
| Language | Details |
|---|---|
| German |
Natalia Strauch, Alina Rehberg
Medizinische Hochschule Hannover
|
| Norwegian Bokmal |
John Tore Valand, Vebjørn Arntzen, Kanika Kuwelker, Marit Alice Venheim
Helse Vest IKT AS, Helse Bergen, Oslo University Hospital
|
| Name | Card | Type | Description |
|---|---|---|---|
|
Title
|
0..* | DV_TEXT |
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'.
|
|
Given name
|
0..* | DV_TEXT |
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.
|
|
Family name
|
0..* | DV_TEXT |
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.
|
|
Suffix
|
0..* | DV_TEXT |
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)'.
|
archetype (adl_version=1.4; uid=c4ed12e0-471f-40ec-b70d-be07ef3c5932) openEHR-EHR-CLUSTER.structured_name.v1 concept [at0000] -- Structured name of a person language original_language = <[ISO_639-1::en]> translations = < ["de"] = < language = <[ISO_639-1::de]> author = < ["name"] = <"Natalia Strauch, Alina Rehberg"> ["organisation"] = <"Medizinische Hochschule Hannover"> ["email"] = <"Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de"> > > ["nb"] = < language = <[ISO_639-1::nb]> author = < ["name"] = <"John Tore Valand, Vebjørn Arntzen, Kanika Kuwelker, Marit Alice Venheim"> ["organisation"] = <"Helse Vest IKT AS, Helse Bergen, Oslo University Hospital"> ["email"] = <"john.tore.valand@helse-vest-ikt.no, varntzen@ous-hf.no, kanika.kuwelker@helse-vest-ikt.no, marit.alice.venheim@helse-vest-ikt.no"> > > > description original_author = < ["name"] = <"Heather Leslie"> ["organisation"] = <"Atomica Informatics"> ["email"] = <"heather.leslie@atomicainformatics.com"> ["date"] = <"2021-04-14"> > details = < ["de"] = < language = <[ISO_639-1::de]> purpose = <"Zur Darstellung von Angaben zu den einzelnen Bestandteilen des Namens einer Person, wie sie im Rahmen der klinischen Dokumentation bekannt sind oder verstanden werden."> use = <"Zur Darstellung von Angaben zu den einzelnen Bestandteilen des Namens einer Person, wie sie im Verlauf der klinischen Dokumentation bekannt sind oder verstanden werden, oft ad hoc oder wenn es nicht angemessen oder möglich ist, ein formelles demografisches Register oder einen Index zu verwenden. In den meisten einfachen Anwendungsfällen für klinische Aufzeichnungen reicht das unstrukturierte Element „Name“ innerhalb des Archetyps CLUSTER.person aus, um den Namen einer Person als Teil einer Gesundheitsakte darzustellen. In Fällen, in denen ein strukturierter Name für klinische Aufzeichnungszwecke erforderlich oder wünschenswert ist, verschachteln Sie diesen Archetyp im SLOT „Name strukturiert“ im Archetyp CLUSTER.person. Jedes Datenelement kann als Zeichenfolge mit freiem Text eingegeben werden – zum Beispiel „Prof Dr“, „Sonja Jane“, „Smith-Brown“, „MP“. Alternativ, da jedes Datenelement innerhalb eines Templates wiederholbar ist: - „Titel“ könnte für den Wert „Prof“ auf „Titel 1“ und für den Wert „Dr“ auf „Titel 2“ geklont werden; und - „Vorname“ konnte geklont und für den Wert „Sonja“ in „Vorname“ und für den Wert „Jane“ in „Zweiter Vorname“ umbenannt werden. Obwohl dieser Archetyp an ISO 22220 ausgerichtet wurde, wurden aufgrund des eingeschränkten Umfangs dieses Archetyps der bevorzugte Name, die Namensverwendung, die Gültigkeitsdaten und die sich wiederholende Gruppierung von Namensbestandteil/Ordnung absichtlich nicht repliziert. Es wird davon ausgegangen, dass in den meisten Anwendungsfällen, für die dieser Archetyp entworfen wurde, komplexe Familiennamen einfach als Zeichenfolge aufgezeichnet werden. Es ist jedoch möglich, sie mit größerer Granularität und innerhalb dieses strukturierten Namensmusters unter Verwendung von Regeln und Beispielen aus ISO 22220:2007 (Anhang F) aufzuzeichnen, einschließlich: - Familienname zuerst, Vorname/n zuletzt; - Familiennamen mit Präfixen z.B. El Haddad oder van der Heyden; und - Namen, die sowohl den Familiennamen des Vaters als auch der Mutter enthalten."> keywords = <"Person, Individuum, Name", ...> misuse = <"Der Achetyp darf nicht verwendet werden, wenn eine unstrukturierte Textzeichenfolge, die den Namen der Person darstellt, für den Zweck geeignet ist. Verwenden Sie zu diesem Zweck das Datenelement „Name“ innerhalb des CLUSTER.person. Darf nicht für komplexe Namensdarstellung oder -verwaltung, wie z. B. Vorzugsnamen, Namensverwendung oder gültige Verwendungsdaten verwendet werden. Verwenden Sie zu diesem Zweck einen formellen Master Patient Index oder Health Provider Index oder Archetypen, die auf dem demografischen Informationsmodell von openEHR basieren. Darf nicht verwendet werden, um das formelle Identifikationsmanagement darzustellen oder zu ersetzen oder um ein offizielles demografisches Register oder einen Index zu führen. Verwenden Sie zu diesem Zweck einen formellen Master Patient Index oder Health Provider Index oder Archetypen, die auf dem demografischen Informationsmodell von openEHR basieren. Darf nicht verwendet werden, um den Behandlungsgegenstand, die Teilnehmer oder den Verfasser der Aufzeichnung und ähnliche Datenelemente darzustellen, die formal in der Patientenakte unter Verwendung der Referenzmodellattribute dargestellt werden sollten."> > ["nb"] = < language = <[ISO_639-1::nb]> purpose = <"For å registrere detaljer om et individs strukturerte navn, som man har informasjon om eller har forstått, i det kliniske dokumentasjonsarbeidet."> use = <"Brukes for å registrere detaljer om et individs strukturerte navn, som man har informasjon om eller har forstått, i det kliniske dokumentasjonsarbeidet. Brukes ofte ad hoc eller i de tilfeller der det ikke er ønskelig eller mulig å bruke et formelt demografisk register eller indeks. I de mest vanlige brukscasene vil det ustrukturerte dataelementet \"Navn\" i arketypen CLUSTER.person være tilstrekkelig til å registrere navnet til en person. Denne arketypen skal brukes i tilfeller der man har behov for detaljer om en eller flere komponenter i navnet, og gjøres ved å benytte denne arketypen i SLOTet \"Strukturert navn\" i arketypen CLUSTER.person. Hver enkelt komponent kan registreres som fritekst, for eksempel: \"Prof Dr\", \"Sonja Jane\", \"Smith Brown\". Alternativt, ettersom hvert dataelement kan repeteres i et templat: - \"Tittel\" kan klones til \"Tittel 1\" for verdien \"Prof\" og \"Tittel 2\" for \"Dr\". - \"Fornavn\" kan klones til \"Fornavn\" for verdien Sonja og \"Mellomnavn\" for verdien \"Jane\". Selv om denne arketypen er laget for å være lik ISO 22220, har foretrukket navn, navnebruk, gyldige datoer og den gjentatte navnekomponenten/rangeringen med hensikt ikke blitt replikert på grunn av at arketypen har et mer begrenset bruksområde. Det antas at i de fleste brukstilfeller som denne arketypen er designet for, vil komplekse familienavn ganske enkelt bli registrert som en streng. ISO 22220:2007 (vedlegg F) gir eksempler og veiledning for hvordan du registrerer komplekse navn innenfor det strukturerte navnemønsteret, inkludert: - Etternavn først, fornavn/navn etter. - Familienavn med prefikser, f.eks. El Haddad eller van der Heyden. - Navn som inneholder både fars og mors etternavn."> keywords = <"person, individ, navn", ...> misuse = <"Brukes ikke dersom det for formålet er tilstrekkelig at personens navn registreres som fritekst. Bruk dataelementet \"Navn\" i CLUSTER.person (Person) for dette formålet. Brukes ikke til kompleks navnerepresentasjon eller administrative oppgaver, for eksempel foretrukne navn, navnebruk eller gyldige bruksdatoer. Bruk et formelt pasientregister, helsepersonellregister eller arketyper basert på openEHR demografisk informasjonsmodell til dette formålet. Brukes ikke til å representere eller erstatte de formelle demografiske detaljene for formell identitetsforvaltning, eller for å opprettholde et demografisk register eller en indeks. Bruk et formelt pasientregister, helsepersonellregister eller arketyper basert på openEHR demografisk informasjonsmodell til dette formålet. Brukes ikke for å representere pasient, deltakere eller forfatter av skjema eller lignende, som skal representeres formelt i pasientjournalen, bruk attributter fra Referansemodellen for dette formålet."> > ["en"] = < language = <[ISO_639-1::en]> purpose = <"To record details about the structured name of an individual as they are known or understood in the course of clinical documentation."> use = <"Use 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."> keywords = <"person, individual, name", ...> misuse = <"Not 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."> copyright = <"© openEHR Foundation"> > > lifecycle_state = <"published"> other_contributors = <"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)"> other_details = < ["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"> > definition CLUSTER[at0000] matches { -- Structured name of a person items cardinality matches {1..*; unordered} matches { ELEMENT[at0001] occurrences matches {0..*} matches { -- Title value matches { DV_TEXT matches {*} } } ELEMENT[at0002] occurrences matches {0..*} matches { -- Given name value matches { DV_TEXT matches {*} } } ELEMENT[at0005] occurrences matches {0..*} matches { -- Family name value matches { DV_TEXT matches {*} } } ELEMENT[at0006] occurrences matches {0..*} matches { -- Suffix value matches { DV_TEXT matches {*} } } } } ontology term_definitions = < ["en"] = < items = < ["at0000"] = < text = <"Structured name of a person"> description = <"Discrete components of an individual's name."> > ["at0001"] = < 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'."> > ["at0005"] = < 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."> > ["at0002"] = < 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."> > ["at0006"] = < 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)'."> > > > ["de"] = < items = < ["at0000"] = < text = <"Strukturierter Name der Person"> description = <"Getrennte Bestandteile des Namens einer Person."> > ["at0001"] = < text = <"Titel"> description = <"Eine oder mehrere ehrenhafte Anrede(n) am Anfang eines Namens."> comment = <"Vorkommen für dieses Datenelement werden auf 0..* gesetzt, damit mehr als ein Titel dargestellt werden können. Die Kodierung mit einer externen Terminologie wird nach Möglichkeit bevorzugt. Beispiel: \"Doktor\", \"Ms\", \"Mx\" oder \"Professor Dr\"."> > ["at0002"] = < text = <"Vorname"> description = <"Ein oder mehrere eindeutige Namen, die verwendet werden, um eine Person innerhalb einer Familiengruppe zu identifizieren. "> comment = <"Vorkommen für dieses Datenelement werden auf 0..* gesetzt, damit mehr als ein Vorname dargestellt werden können. Darüber hinaus kann dieses Datenelement innerhalb eines Templates geklont und umbenannt werden, um eine getrennte Darstellung verschiedener Arten von Vornamen zu ermöglichen – zum Beispiel „Vorname“, „Zweiter Vorname“, „bevorzugter Name“ oder „Spitzname“, wie für einen konkreten Anwendungsfall erforderlich."> > ["at0005"] = < text = <"Nachname"> description = <"Ein oder mehrere Namen, die eine Person mit einer Familiengruppe gemeinsam hat."> comment = <"Auch bekannt als „Familienname“. Vorkommen für dieses Datenelement werden auf 0..* gesetzt, damit mehr als ein Familienname dargestellt werden können. Komplexe Namen wie „El Haddad“ oder „van der Heyden“ können mit diesem Benennungsmuster dargestellt werden, wie in ISO 22220 (Anhang F) definiert, aber für den beabsichtigten Anwendungsfall für diesen Archetyp ist es am wahrscheinlichsten, dass der vollständige Nachname als Zeichenfolge aufgezeichnet wird."> > ["at0006"] = < text = <"Suffix"> description = <"Ein oder mehrere Begriffe, die allen anderen Namensbestandteilen nachgestellt werden, normalerweise um eine Person von einem Familienmitglied mit identischen Vor- und Nachnamensbestandteilen zu unterscheiden."> comment = <"Vorkommen für dieses Datenelement werden auf 0..* gesetzt, damit mehr als ein Suffix aufgezeichnet werden können. Die Codierung mit einer externen Terminologie wird nach Möglichkeit bevorzugt. Zum Beispiel: „Junior (Jr)“, „Senior (Sr)“, \" Der Zweite (II)\"."> > > > ["nb"] = < items = < ["at0000"] = < text = <"Strukturert navn"> description = <"Detaljer om de ulike enkeltkomponentene i en person sitt navn."> > ["at0001"] = < text = <"Tittel"> description = <"En eller flere tiltaleform(er) plassert foran de andre navnekomponentene."> comment = <"Forekomster for dette dataelementet er satt til 0..* slik at mer enn én tittel kan registreres. Koding med ekstern terminologi foretrekkes der det er mulig. For eksempel: \"Doktor\"; \"Fru\"; \"Herr\"; eller \"Professor dr\"."> > ["at0002"] = < text = <"Fornavn"> description = <"Ett eller flere unike navn som unikt identifiserer vedkommende i en familie."> comment = <"Forekomster for dette dataelementet er satt til 0..* slik at mer enn ett \"Fornavn\" kan registreres. I tillegg kan dette dataelementet klones og gis et nytt navn i et templat for å tillate registrering av \"Fornavn\", \"Mellomnavn\" og \"Kallenavn\" eller liknende typer fornavn, som kreves for et spesifikt brukstilfelle. På engelsk er fornavn kjent som en del av \"Given name\"."> > ["at0005"] = < text = <"Etternavn"> description = <"Ett eller flere unike navn som unikt identifiserer vedkommende med en familie."> comment = <"Forekomster for dette dataelementet er satt til 0..* slik at mer en ett \"Etternavn\" kan registreres. Også kjent som \"Slektsnavn\" eller \"Familienavn\". Komplekse navn som for eksempel \"El Haddad\" eller \"van der Heyden\" kan registreres ved å bruke dette navnemønsteret som i ISO 22220 (Annex F), men det antas at i de fleste brukstilfeller som denne arketypen er designet for, vil komplekse familienavn ganske enkelt bli registrert som en streng."> > ["at0006"] = < text = <"Suffiks"> description = <"En eller flere termer som legges etter alle de andre komponentene i en persons navn, vanligvis for å skille ulike familiemedlemmer med identiske fornavn- og etternavnkomponenter."> comment = <"Forekomster for dette dataelementet er satt til 0..* slik at mer en ett \"Suffiks\" kan registreres. Koding med en ekstern terminologi er foretrukket, hvor mulig. For eksempel: \"Junior (Jr)\", \"Senior (Sr)\" og \"Den Andre (II)\"."> > > > >