Extensions for Using Data Elements from FHIR STU3 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R3-name-assembly-order-for-R5 | Version: 0.1.0 | |||
| Standards status: Trial-use | Maturity Level: 0 | Computable Name: R3NameAssemblyOrderForR5 | ||
This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/name-assembly-order|3.0.2 for use in FHIR R5.
This value set is part of the cross-version definitions generated to enable use of the
value set http://hl7.org/fhir/ValueSet/name-assembly-order|3.0.2 as defined in FHIR STU3
in FHIR R5.
The source value set is bound to the following FHIR STU3 elements:
Across FHIR versions, the value set has been mapped as:
http://hl7.org/fhir/ValueSet/name-assembly-order|3.0.2http://hl7.org/fhir/ValueSet/name-assembly-order|4.0.1http://hl7.org/fhir/ValueSet/name-assembly-order|4.3.0Note that all concepts are included in this cross-version definition because no concepts have compatible representations
Following are the generation technical comments:
All concepts in the comparison are listed as identical.
The source and target value sets have the same number of active concepts (7).
All concepts in the comparison are listed as identical.
The source and target value sets have the same number of active concepts (7).
FHIR ValueSet http://hl7.org/fhir/ValueSet/name-assembly-order|3.0.2, defined in FHIR STU3 does not have any mapping to FHIR R5
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
This value set includes codes based on the following rules:
http://hl7.org/fhir/name-assembly-order version 📍3.0.2| Code | Display |
| NL1 | Own Name |
| NL2 | Partner Name |
| NL3 | Partner Name followed by Maiden Name |
| NL4 | Own Name followed by Partner Name |
http://hl7.org/fhir/v2/0444 version 📍2.8.2
| Code | Display |
| F | Prefix Family Given Suffix |
| G | Prefix Given Family Suffix |
http://hl7.org/fhir/v3/NullFlavor version 📍2016-11-11
| 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: 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 expansion contains 7 concepts.
| System | Version | Code | Display | Definition | JSON | XML |
http://hl7.org/fhir/name-assembly-order | 3.0.2 | NL1 | Own Name | |||
http://hl7.org/fhir/name-assembly-order | 3.0.2 | NL2 | Partner Name | |||
http://hl7.org/fhir/name-assembly-order | 3.0.2 | NL3 | Partner Name followed by Maiden Name | |||
http://hl7.org/fhir/name-assembly-order | 3.0.2 | NL4 | Own Name followed by Partner Name | |||
http://hl7.org/fhir/v2/0444 | 2.8.2 | F | Prefix Family Given Suffix | |||
http://hl7.org/fhir/v2/0444 | 2.8.2 | G | Prefix Given Family Suffix | |||
http://hl7.org/fhir/v3/NullFlavor | 2016-11-11 | UNK | Unknown | Description:A proper value is applicable, but not known.
|
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 |