Release 5 Preview #2

This page is part of the FHIR Specification (v4.4.0: R5 Preview #2). 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

4.4.1.213 Value Set http://hl7.org/fhir/ValueSet/name-assembly-order

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/name-assembly-order
Version:4.4.0
Name:HumanNameAssemblyOrder
Title:HumanNameAssemblyOrder
Definition:

A code that represents the preferred display order of the components of a human name.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.913 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is not currently used

4.4.1.213.1 Content Logical Definition

  • Include all codes defined in http://terminology.hl7.org/CodeSystem/name-assembly-order
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0444
    CodeDisplay
    FPrefix Family Given Suffix
    GPrefix Given Family Suffix
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
    CodeDisplay
    UNKUnknownDescription: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:
    Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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 value set includes codes based on the following rules:

 

4.4.1.213.2 Expansion

This expansion generated 03 May 2020

This value set contains 7 concepts

CodeSystemDisplayLogical Definition (CLD)
NL1http://terminology.hl7.org/CodeSystem/name-assembly-orderOwn Name
NL2http://terminology.hl7.org/CodeSystem/name-assembly-orderPartner Name
NL3http://terminology.hl7.org/CodeSystem/name-assembly-orderPartner Name followed by Maiden Name
NL4http://terminology.hl7.org/CodeSystem/name-assembly-orderOwn Name followed by Partner Name
Fhttp://terminology.hl7.org/CodeSystem/v2-0444Prefix Family Given Suffix
Ghttp://terminology.hl7.org/CodeSystem/v2-0444Prefix Given Family Suffix
UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorUnknownDescription: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: Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 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.)

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code