FHIR Extensions Pack
5.1.0-snapshot1 - Working Copy International flag

This page is part of the FHIR Core Extensions Registry (v5.1.0-snapshot1: Release 5.1) based on FHIR (HL7® FHIR® Standard) v5.0.0. The current version which supersedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

ValueSet: HumanNameAssemblyOrder

Official URL: http://hl7.org/fhir/ValueSet/name-assembly-order Version: 5.1.0-snapshot1
Standards status: Trial-use Maturity Level: 3 Computable Name: HumanNameAssemblyOrder
Other Identifiers: urn:ietf:rfc:3986#Uniform Resource Identifier (URI)#urn: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:

  • No changes

    • Logical Definition (CLD)

    This value set includes codes based on the following rules:

    • 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
      CodeDisplayDefinition
      FPrefix Family Given SuffixPrefix Family Middle Given Suffix
      GPrefix Given Family SuffixPrefix Given Middle Family Suffix
    • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor
      CodeDisplayDefinition
      UNKUnknown**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.)

     

    Expansion

    This value set contains 7 concepts.

    CodeSystemDisplayDefinition
      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

    Prefix Family Middle Given Suffix

      Ghttp://terminology.hl7.org/CodeSystem/v2-0444Prefix Given Family Suffix

    Prefix Given Middle Family Suffix

      UNKhttp://terminology.hl7.org/CodeSystem/v3-NullFlavorUnknown

    **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.)

    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