This
page
is
part
of
the
FHIR
Specification
(v3.3.0:
(v3.5.0:
R4
Ballot
2).
#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
FHIR
Infrastructure
Work
Group
|
Maturity Level : 0 | Informative | 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: | 3.5.0 |
| Name: | HumanNameAssemblyOrder |
| Title: | HumanNameAssemblyOrder |
| Definition: |
A
code
that
represents
the
preferred
display
order
of
the
components
of
a
human
|
| Committee: |
FHIR
Infrastructure
Work
Group
|
| OID: | 2.16.840.1.113883.4.642.3.913 (for OID based terminology systems) |
| Source Resource | XML / JSON |
This value set is used in the following places:
This value set includes codes from the following code systems:
http://hl7.org/fhir/name-assembly-order
http://terminology.hl7.org/CodeSystem/name-assembly-order
http://hl7.org/fhir/v2/0444
http://terminology.hl7.org/CodeSystem/v2-0444
| Code | Display | |
| F | Prefix Family Given Suffix | |
| G | Prefix Given Family Suffix |
http://hl7.org/fhir/v3/NullFlavor
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
| Code | Display | |
| 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: 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
expansion
generated
03
Apr
19
Aug
2018
This value set contains 7 concepts
Expansion
based
on
http://hl7.org/fhir/v3/NullFlavor
http://terminology.hl7.org/CodeSystem/name-assembly-order
version
2018-04-01,
http://hl7.org/fhir/name-assembly-order
3.5.0,
http://terminology.hl7.org/CodeSystem/v2-0444
version
3.3.0,
http://hl7.org/fhir/v2/0444
2.9,
http://terminology.hl7.org/CodeSystem/v3-NullFlavor
version
2.9
2018-08-12
| Code | System | Display | Definition |
| NL1 |
|
Own Name | |
| NL2 |
|
Partner Name | |
| NL3 |
|
Partner Name followed by Maiden Name | |
| NL4 |
|
Own Name followed by Partner Name | |
| F |
|
Prefix Family Given Suffix | |
| G |
|
Prefix Given Family Suffix | |
| 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: 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:
| 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 |