HL7 v2.9.1 Vocabulary
0.2.0 - ci-build

HL7 v2.9.1 Vocabulary, published by HL7/FO. This guide is not an authorized publication; it is the continuous build for version 0.2.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/frankoemig/hl7.v2.terminology.v291/ and changes regularly. See the Directory of published versions

## : Address Usage (2.9.1 - 1.0.1) - XML Representation

Active as of 2026-03-13

Raw xml | Download

    <CodeSystem xmlns="http://hl7.org/fhir">
      <id value="addressUsage"/>
      <text>
        <status value="generated"/>
        <div xmlns="http://www.w3.org/1999/xhtml"><ul><li>Include all codes defined in <a href="CodeSystem-addressUsage.html"><code>http://terminology.hl7.org/v2plusvocab/CodeSystem/addressUsage</code></a></li></ul></div>
      </text>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-v2versionCreated">
        <valueString value="2.9.1"/>
      </extension>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-versionHistory">
        <valueString value="generate correct history somehow"/>
      </extension>
      <extension
                 url="http://terminology.hl7.org/v2plusvocab/StructureDefinition/codesystem-tableNo">
        <valueString value="0617"/>
      </extension>
      <url
           value="http://terminology.hl7.org/v2plusvocab/CodeSystem/addressUsage"/>
      <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="urn:oid:2.16.840.1.113883.18.375"/>
      </identifier>
      <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="http://terminology.hl7.org/v2plusvocab/CodeSystem/v2-0617"/>
      </identifier>
      <version value="1.0.1"/>
      <name value="AddressUsage"/>
      <title value="Address Usage (2.9.1 - 1.0.1)"/>
      <status value="active"/>
      <experimental value="true"/>
      <date value="2026-03-13T11:04:57+00:00"/>
      <publisher value="HL7/FO"/>
      <contact>
        <name value="HL7/FO"/>
        <telecom>
          <system value="url"/>
          <value value="http://www.hl7.org"/>
        </telecom>
      </contact>
      <description
                   value="HL7-defined code system of concepts specifying how an address is intended to be used.  Used in HL7 Version 2.x messaging in the XAD segment."/>
      <copyright value="HL7 Inc., 2026"/>
      <caseSensitive value="true"/>
      <compositional value="false"/>
      <content value="complete"/>
      <property>
        <code value="versionIntroduced"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionIntroduced"/>
        <description value="version when was this code introduced"/>
        <type value="string"/>
      </property>
      <property>
        <code value="versionDeprecated"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#versionDeprecated"/>
        <description value="version when was this code deprecated"/>
        <type value="string"/>
      </property>
      <property>
        <code value="status"/>
        <uri value="http://hl7.org/fhir/concept-properties#status"/>
        <description
                     value="A code that indicates the status of the concept. Typical values are active, experimental, deprecated, and retired"/>
        <type value="code"/>
      </property>
      <property>
        <code value="comment"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#comment"/>
        <description
                     value="A string that provides additional detail pertinent to the use or understanding of the concept"/>
        <type value="string"/>
      </property>
      <property>
        <code value="usage"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#usage"/>
        <description value="usage notes for this code"/>
        <type value="string"/>
      </property>
      <property>
        <code value="modified"/>
        <uri
             value="http://terminology.hl7.org/v2plusvocab/CodeSystem/Property#modified"/>
        <description value="date of last modification"/>
        <type value="dateTime"/>
      </property>
      <concept id="6261">
        <code value="C"/>
        <display value="Classification"/>
        <definition value="Classification"/>
        <property>
          <code value="comment"/>
          <valueString
                       value="Identifies an address used for the purpose of demographic classification or searching.  Such addresses frequently contain insufficient information to be used as mailing or visit addresses.  For example, they may only indicate country and postal code, without providing a street address."/>
        </property>
        <property>
          <code value="modified"/>
          <valueDateTime value="2015-07-13"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.6"/>
        </property>
      </concept>
      <concept id="6259">
        <code value="M"/>
        <display value="Mailing"/>
        <definition value="Mailing"/>
        <property>
          <code value="comment"/>
          <valueString
                       value="Identifies an address for mail correspondence from a healthcare provider as stipulated by the subject.
    For example, under the tenets of certain privacy regulations, it is exclusive to the patient and is typically maintained at the encounter or visit level versus the person level as it only has relevance to the specifics of a given encounter.  This is an exception category of address in that the patient has stipulated that they want all correspondence relevant to a given encounter sent to this address in lieu of any other address on file.  Providers are required to accommodate such requests under HIPAA promulgated regulation.  Note that mailing and legal address may be mutually exclusive as defined below.  (Implementors are reminded that although the privacy regulation requires the provider to honor such requests, it does require the provider to enquire whether the patient has a preferred address other than the one volunteered.)"/>
        </property>
        <property>
          <code value="modified"/>
          <valueDateTime value="2015-07-13"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.6"/>
        </property>
      </concept>
      <concept id="6260">
        <code value="V"/>
        <display value="Visit"/>
        <definition value="Visit"/>
        <property>
          <code value="comment"/>
          <valueString
                       value="Identifies an address at which the individual is physically located and may be visited."/>
        </property>
        <property>
          <code value="modified"/>
          <valueDateTime value="2015-07-13"/>
        </property>
        <property>
          <code value="versionIntroduced"/>
          <valueString value="2.6"/>
        </property>
      </concept>
    </CodeSystem>