FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4B
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R5 from FHIR R4B - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R4B.HumanNameAssemblyOrder for use in FHIR R5

Official URL: http://hl7.org/fhir/4.3/ValueSet/R4B-name-assembly-order-for-R5 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R4B_name_assembly_order_for_R5

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/name-assembly-order 4.3.0 for use in FHIR R5. Concepts not present here have direct equivalent mappings crossing all versions from R4B to R5.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

This value set includes codes based on the following rules:

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/name-assembly-order version 4.3.0
    CodeDisplay
    NL1Own Name
    NL2Partner Name
    NL3Partner Name followed by Maiden Name
    NL4Own Name followed by Partner Name
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v2-0444 version 4.3.0
    CodeDisplayDefinition
    F Prefix Family Given Suffix Prefix Family Middle Given Suffix
    G Prefix Given Family Suffix Prefix Given Middle Family Suffix
  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-NullFlavor version 4.3.0
    CodeDisplayDefinition
    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.)

 

Expansion

This value set expansion 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 SuffixPrefix Family Middle Given Suffix
  Ghttp://terminology.hl7.org/CodeSystem/v2-0444Prefix Given Family SuffixPrefix 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