This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Definition for Value SetHumanNameAssemblyOrder
<?xml version="1.0" encoding="UTF-8"?> <ValueSet xmlns="http://hl7.org/fhir"> <id value="name-assembly-order"/> <meta> <lastUpdated value="2019-12-31T21:03:40.621+11:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> HumanNameAssemblyOrder</h2> <div> <p> A code that represents the preferred display order of the components of a human name.</p> </div> <p> This value set includes codes from the following code systems:</p> <ul> <li> Include all codes defined in <a href="codesystem-name-assembly-order.html"> <code> http://terminology.hl7.org/CodeSystem/name-assembly-order</code> </a> </li> <li> Include these codes as defined in <a href="v2/0444/index.html"> <code> http://terminology.hl7.org/CodeSystem/v2-0444</code> </a> <table class="none"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> </tr> <tr> <td> <a href="v2/0444/index.html#v2-0444-F">F</a> </td> <td> Prefix Family Given Suffix</td> <td/> </tr> <tr> <td> <a href="v2/0444/index.html#v2-0444-G">G</a> </td> <td> Prefix Given Family Suffix</td> <td/> </tr> </table> </li> <li> Include these codes as defined in <a href="v3/NullFlavor/cs.html"> <code> http://terminology.hl7.org/CodeSystem/v3-NullFlavor</code> </a> <table class="none"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> </tr> <tr> <td> <a href="v3/NullFlavor/cs.html#v3-NullFlavor-UNK">UNK</a> </td> <td> Unknown</td> <td> Description:A proper value is applicable, but not known. <br/> 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: <br/> 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.) </td> </tr> </table> </li> </ul> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="fhir"/> </extension> <url value="http://hl7.org/fhir/ValueSet/name-assembly-order"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.3.913"/> </identifier> <version value="4.2.0"/> <name value="HumanNameAssemblyOrder"/> <title value="HumanNameAssemblyOrder"/> <status value="draft"/> <experimental value="false"/> <date value="2019-12-31T21:03:40+11:00"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <description value="A code that represents the preferred display order of the components of a human name."/> <immutable value="true"/> <compose> <include> <system value="http://terminology.hl7.org/CodeSystem/name-assembly-order"/> </include> <include> <system value="http://terminology.hl7.org/CodeSystem/v2-0444"/> <concept> <code value="F"/> <display value="Prefix Family Given Suffix"/> </concept> <concept> <code value="G"/> <display value="Prefix Given Family Suffix"/> </concept> </include> <include> <system value="http://terminology.hl7.org/CodeSystem/v3-NullFlavor"/> <concept> <code value="UNK"/> <display value="Unknown"/> </concept> </include> </compose> </ValueSet>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.