This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Country: World, Country: World |
Official URL: http://hl7.org/fhir/ValueSet/name-assembly-order
|
Version: 5.0.0-snapshot3 | |||
draft as of 2022-12-14 | Computable Name: HumanNameAssemblyOrder | |||
Flags: Immutable | OID: 2.16.840.1.113883.4.642.3.913 |
This value set is not currently used
A code that represents the preferred display order of the components of a human name.
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/name-assembly-order
http://terminology.hl7.org/CodeSystem/v2-0444
Code | Display | Definition |
F | Prefix Family Given Suffix | Prefix Family Middle Given Suffix |
G | Prefix Given Family Suffix | Prefix Given Middle Family Suffix |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
Code | Display | Definition |
UNK | Unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |
This expansion generated 14 Dec 2022
This value set contains 7 concepts
Expansion based on:
Code | System | Display | Definition |
NL1 | http://terminology.hl7.org/CodeSystem/name-assembly-order | Own Name | |
NL2 | http://terminology.hl7.org/CodeSystem/name-assembly-order | Partner Name | |
NL3 | http://terminology.hl7.org/CodeSystem/name-assembly-order | Partner Name followed by Maiden Name | |
NL4 | http://terminology.hl7.org/CodeSystem/name-assembly-order | Own Name followed by Partner Name | |
F | http://terminology.hl7.org/CodeSystem/v2-0444 | Prefix Family Given Suffix | Prefix Family Middle Given Suffix |
G | http://terminology.hl7.org/CodeSystem/v2-0444 | Prefix Given Family Suffix | Prefix Given Middle Family Suffix |
UNK | http://terminology.hl7.org/CodeSystem/v3-NullFlavor | Unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
|
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
Definition | An explanation of the meaning of the concept |
Comments | Additional notes about how to use the code |