This page is part of the FHIR Core Extensions Registry (v5.2.0-ballot: Release 5.2) based on FHIR (HL7® FHIR® Standard) v5.0.0. The current version which supersedes this version is 5.1.0. For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/fhir/ValueSet/name-assembly-order | Version: 5.2.0-ballot | |||
Standards status: Trial-use | Maturity Level: 3 | Computable Name: HumanNameAssemblyOrder | ||
Other Identifiers: OID:2.16.840.1.113883.4.642.3.913 |
A code that represents the preferred display order of the components of a human name.
References
Changes since version 1.0.0:
Generated Narrative: ValueSet name-assembly-order
Last updated: 2023-01-31 07:07:38+1100
Profile: Shareable ValueSet
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.) |
Generated Narrative: ValueSet
Last updated: 2023-01-31 07:07:38+1100
Profile: Shareable ValueSet
Expansion based on:
This value set contains 7 concepts
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:
|
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |