Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Example ConceptMap/101 (XML)

Terminology Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

Raw XML (canonical form + also see XML Format Specification)

Jump past Narrative

General ConceptMap Example (id = "101")

<?xml version="1.0" encoding="UTF-8"?>

<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="101"/> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2> FHIRv3AddressUse (http://hl7.org/fhir/ConceptMap/101)</h2> 
      <p> Mapping from 
        <a href="valueset-address-use.html">AddressUse</a>  to 
        <a href="http://terminology.hl7.org/5.1.0/ValueSet-v3-AddressUse.html">AddressUse</a> 
      </p> 
      <p> DRAFT (not intended for production usage). Published on 2012-06-13 by HL7, Inc
         (FHIR project team (example): 
        <a href="http://hl7.org/fhir">http://hl7.org/fhir</a> ). Creative Commons 0
      </p> 
      <div> 
        <p> A mapping between the FHIR and HL7 v3 AddressUse Code systems</p> 

      </div> 
      <br/>  
      <p> 
        <b> Group 1</b> Mapping from 
        <a href="codesystem-address-use.html">AddressUse</a>  to 
        <a href="http://terminology.hl7.org/5.1.0/CodeSystem-v3-AddressUse.html">AddressUse</a> 
      </p> 
      <table class="grid">
        <tr> 
          <td> 
            <b> Source Code</b> 
          </td> 
          <td> 
            <b> Relationship</b> 
          </td> 
          <td> 
            <b> Target Code</b> 
          </td> 
          <td> 
            <b> Comment</b> 
          </td> 
        </tr> 
        <tr> 
          <td> home</td> 
          <td> 
            <a href="codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a> 
          </td> 
          <td> H (home address)</td> 
          <td/>  
        </tr> 
        <tr> 
          <td> work</td> 
          <td> 
            <a href="codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a> 
          </td> 
          <td> WP (work place)</td> 
          <td/>  
        </tr> 
        <tr> 
          <td> temp (Temporary)</td> 
          <td> 
            <a href="codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a> 
          </td> 
          <td> TMP (temporary address)</td> 
          <td/>  
        </tr> 
        <tr> 
          <td> old (Old / Incorrect)</td> 
          <td> 
            <a href="codesystem-concept-map-relationship.html#not-related-to" title="not-related-to">is not related to</a> 
          </td> 
          <td> BAD (bad address)</td> 
          <td> In the HL7 v3 AD, old is handled by the usablePeriod element, but you have to provide
             a time, there's no simple equivalent of flagging an address as old</td> 
        </tr> 
      </table> 
    </div> 
  </text> 
  <url value="http://hl7.org/fhir/ConceptMap/101"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.14.1"/> 
  </identifier> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:uuid:53cd62ee-033e-414c-9f58-3ca97b5ffc3b"/> 
  </identifier> 
  <version value="5.0.0"/> 
  <name value="FHIRv3AddressUse"/> 
  <title value="FHIR/v3 Address Use Mapping"/> 
  <status value="draft"/> 
  <experimental value="true"/> 
  <date value="2012-06-13"/> 
  <publisher value="HL7, Inc"/> 
  <contact> 
    <name value="FHIR project team (example)"/> 
    <telecom> 
      <system value="url"/> 
      <value value="http://hl7.org/fhir"/> 
    </telecom> 
  </contact> 
  <description value="A mapping between the FHIR and HL7 v3 AddressUse Code systems"/> 
  <useContext> 
    <code> 
      <system value="http://terminology.hl7.org/CodeSystem/usage-context-type"/> 
      <code value="venue"/> 
    </code> 
    <valueCodeableConcept> 
      <text value="for CCDA Usage"/> 
    </valueCodeableConcept> 
  </useContext> 
  <jurisdiction> 
    <coding> 
      <system value="urn:iso:std:iso:3166"/> 
      <code value="US"/> 
    </coding> 
  </jurisdiction> 
  <purpose value="To help implementers map from FHIR to HL7 v3/CDA"/> 
  <copyright value="Creative Commons 0"/> 
  <sourceScopeUri value="http://hl7.org/fhir/ValueSet/address-use"/> 
  <targetScopeUri value="http://terminology.hl7.org/ValueSet/v3-AddressUse"/> 
  <group> 
    <source value="http://hl7.org/fhir/address-use"/> 
    <target value="http://terminology.hl7.org/CodeSystem/v3-AddressUse"/> 
    <element> 
      <code value="home"/> 
      <display value="Home"/> 
      <target> 
        <code value="H"/> 
        <display value="home address"/> 
        <relationship value="equivalent"/> 
      </target> 
    </element> 
    <element> 
      <code value="work"/> 
      <display value="Work"/> 
      <target> 
        <code value="WP"/> 
        <display value="work place"/> 
        <relationship value="equivalent"/> 
      </target> 
    </element> 
    <element> 
      <code value="temp"/> 
      <display value="Temporary"/> 
      <target> 
        <code value="TMP"/> 
        <display value="temporary address"/> 
        <relationship value="equivalent"/> 
      </target> 
    </element> 
    <element> 
      <code value="old"/> 
      <display value="Old / Incorrect"/> 
      <target> 
        <code value="BAD"/> 
        <display value="bad address"/> 
        <relationship value="not-related-to"/> 
        <comment value="In the HL7 v3 AD, old is handled by the usablePeriod element, but you have to provide
         a time, there's no simple equivalent of flagging an address as old"/> 
      </target> 
    </element> 
    <unmapped> 
      <mode value="fixed"/> 
      <code value="temp"/> 
      <display value="temp"/> 
      <relationship value="related-to"/> 
    </unmapped> 
  </group> 
</ConceptMap> 

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.