<mappingSpaces>
	<!--
  <space>
    <url>[the formal URL - should also resolve to a useful document if possible]</url>
    <columnName>The name for the mapping in the spreadsheet</columnName>
    <title>The title for the mapping when displayed in the specification</title>
    <id>the internal id on the page for the spec</id>
    <preamble>[if necessary, an xhtml preamble for the mapping]</preamble>
    <sort>[int: The order in which the mappings appear on the mapping page]</sort>
  </space>
  -->
	<space>
		<url>http://hl7.org/fhir/fivews</url>
    <link>http://hl7.org/fhir/fivews.html</link>
		<columnName>[w5]</columnName>
		<title>FiveWs Pattern Mapping</title>
		<id>w5</id>
		<sort>-1</sort>
		<publish>true</publish>
    <sparse>true</sparse>
    <pattern>true</pattern>
	</space>
	<space>
		<url>http://hl7.org/fhir/workflow</url>
		<link>http://hl7.org/fhir/workflow-module.html</link>
		<columnName>Workflow Mapping</columnName>
		<title>Workflow Pattern</title>
		<id>workflow</id>
		<sort>0</sort>
		<publish>true</publish>
    <sparse>true</sparse>
    <pattern>true</pattern>
	</space>
	<space>
		<url>http://hl7.org/fhir/interface</url>
		<link>http://hl7.org/fhir/participant.html</link>
		<columnName>Interface Mapping</columnName>
		<title>Interface Pattern</title>
		<id>interface</id>
		<sort>0</sort>
		<publish>true</publish>
    <sparse>true</sparse>
    <pattern>true</pattern>
	</space>
	<space>
		<url>http://hl7.org/v2</url>
    <link>http://www.hl7.org/implement/standards/product_brief.cfm?product_id=185</link>
		<columnName>v2 Mapping</columnName>
		<title>HL7 V2 Mapping</title>
		<id>v2</id>
		<sort>1</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://loinc.org</url>
		<columnName>LOINC Field Name</columnName>
		<title>LOINC code for the element</title>
		<id>loinc</id>
		<sort>2</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://snomed.org/attributebinding</url>
    <link>http://snomed.org/attributebinding</link>
		<columnName>SNOMED CT Attribute</columnName>
		<title>SNOMED CT Attribute Binding</title>
		<id>sct-attr</id>
		<preamble>
			<p>
      Attribute bindings link coded data elements in FHIR resources to a corresponding attribute in the SNOMED CT concept model. These bindings help to support:
      </p>
      <ul>
        <li>clarifying the intended meaning of the data element</li>
        <li>Quality checking the alignment between FHIR resource design and any coresponding SNOMED CT concept model</li>
        <li>Composition and decomposition of data instances by indicating the SNOMED CT concept model attribute whose value may be used to decompose a precoordinated concept into this data element</li>
      </ul>
		</preamble>
		<sort>3</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://snomed.info/conceptdomain</url>
    <link>http://snomed.info/conceptdomain</link>
		<columnName>SNOMED CT Concept Domain</columnName>
		<title>SNOMED CT Concept Domain Binding</title>
		<id>sct-concept</id>
		<preamble>
			<p>
      Concept domain bindings link a resource or an element to a set of SNOMED CT concepts that represent the intended semantics of the instances (whether or not SNOMED CT is used to encode that data element).
      This set of concepts is represented using a SNOMED CT expression constraint. Note that the 'Concept domain binding' may be a superset of the 'value set binding'. These bindings help to support:
      </p>
      <ul>
        <li>Quality checking FHIR resources by ensuring that (a) the intended semantics of the instances matches the valid range of the corresponding SNOMED CT attribute, and (b) the intended value set is appropriate for the intended semantics of the instances</li>
        <li>Semantic checking of data instances by helping to detect potential inconsistencies caused by overlap between the semantics incorporated in two concept domains</li>
      </ul>
		</preamble>
		<sort>4</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/v3/cda</url>
    <link>http://www.hl7.org/implement/standards/product_brief.cfm?product_id=7</link>
		<columnName>CDA Mapping</columnName>
		<title>CDA (R2)</title>
		<id>cda</id>
		<sort>5</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/v3</url>
    <link>http://www.hl7.org/implement/standards/product_brief.cfm?product_id=186</link>
		<columnName>RIM Mapping</columnName>
		<title>RIM Mapping</title>
		<id>rim</id>
		<sort>6</sort>
    <publish>true</publish>
    <sparse>true</sparse>
	</space>
	<space>
		<url>http://nema.org/dicom</url>
		<link>https://www.dicomstandard.org/current</link>
		<columnName>DICOM Mapping</columnName>
		<title>DICOM Tag Mapping</title>
		<id>dicom</id>
		<sort>7</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://w3.org/vcard</url>
    <link>https://tools.ietf.org/html/rfc6350</link>
		<columnName>vCard Mapping</columnName>
		<title>vCard Mapping</title>
		<id>vcard</id>
		<sort>8</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://ihe.net/xds</url>
    <link>http://wiki.ihe.net/index.php/Category:DocShare</link>
		<columnName>XDS Mapping</columnName>
		<title>XDS metadata equivalent</title>
		<id>xds</id>
		<sort>9</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://www.w3.org/ns/prov</url>
		<link>http://www.w3.org/ns/prov</link>
		<columnName>Prov Mapping</columnName>
		<title>W3C PROV</title>
		<id>w3c.prov</id>
		<preamble>
			<p>
      The provenance resource is based on known practices in the
      HL7 implementation space, particularly those found in the
      v2 EVN segment, the v3 ControlAct Wrapper, the CDA header, and
      IHE ATNA.
      The conceptual model underlying the design is the <a href="http://www.w3.org/2011/prov/wiki/Main_Page">W3C
      provenance Specification</a>. Though the content and format
      of the resource is designed to meet specific requirements for FHIR,
      all the parts of the resource are formally mapped to the PROV-O
      specification, and FHIR resources can be transformed to their W3C
      PROV equivalent.
     </p>
		</preamble>
		<sort>10</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://ietf.org/rfc/2445</url>
		<link>http://www.ietf.org/rfc/rfc2445.txt</link>
		<columnName>iCal Mapping</columnName>
		<title>iCalendar</title>
		<id>ical</id>
		<sort>11</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://www.omg.org/spec/ServD/1.0/</url>
		<link>http://www.omg.org/spec/ServD/1.0/</link>
		<columnName>ServD Mapping</columnName>
		<title>ServD</title>
		<id>servd</id>
		<sort>12</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://metadata-standards.org/11179/</url>
		<link>http://metadata-standards.org/11179/</link>
		<columnName>11179 Mapping</columnName>
		<title>ISO 11179</title>
		<id>iso11179</id>
		<preamble>
			<p>
      These mappings are included to indicate where properties of the data elements defined by the FHIR specification relate to similar fields in the ISO 11179 specification.
     </p>
		</preamble>
		<sort>13</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://ihe.net/data-element-exchange</url>
		<link>http://wiki.ihe.net/index.php?title=Data_Element_Exchange</link>
		<columnName>IHE DEX mapping</columnName>
		<title>IHE Data Element Exchange (DEX)</title>
		<id>dex</id>
		<sort>14</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://openehr.org</url>
		<link>http://openehr.org</link>
		<columnName>OpenEHR mapping</columnName>
		<title>Open EHR Archetype Mapping</title>
		<id>openehr</id>
		<sort>15</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://siframework.org/ihe-sdc-profile</url>
		<link>http://wiki.siframework.org/IHE+SDC+Profile</link>
		<columnName>IHE SDC mapping</columnName>
		<title>IHE Structured Data Capture</title>
		<id>ihesdc</id>
		<sort>16</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://siframework.org/cqf</url>
		<link>http://wiki.siframework.org/CQF</link>
		<columnName>QUICK mapping</columnName>
		<title>Quality Improvement and Clinical Knowledge (QUICK)</title>
		<id>quick</id>
		<sort>17</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://www.cdisc.org/define-xml</url>
		<columnName>CDISC Define.xml 2.0 Mapping</columnName>
		<title>CDISC Define XML 2.0 metadata standard</title>
		<id>define.xml2.0</id>
		<sort>18</sort>
		<publish>true</publish>
	</space>
<!--	<space>
		<url>http://www.cdisc.org/define-xml</url>
		<columnName>CDISC Define.xml 2.0 Mapping</columnName>
		<title>CDISC Define XML 2.0 metadata standard</title>
		<id>define.xml2.0</id>
		<sort>19</sort>
		<publish>true</publish>
	</space> -->
	<space>
		<url>http://www.cda-adc.ca/en/services/cdanet/</url>
		<link>http://www.cda-adc.ca/en/services/cdanet/</link>
		<columnName>CDAnet v4 Mapping</columnName>
		<title>Canadian Dental Association eclaims standard</title>
		<id>cdanetv4</id>
		<sort>20</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://www.pharmacists.ca/</url>
		<link>http://www.pharmacists.ca/</link>
		<columnName>CPhA3 (Pharmacy) Mapping</columnName>
		<title>Canadian Pharmacy Association eclaims standard</title>
		<id>cpha3pharm</id>
		<sort>21</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://www.healthit.gov/quality-data-model</url>
		<link>http://www.healthit.gov/quality-data-model</link>
		<columnName>QDM Mapping</columnName>
		<title>Quality Data Model</title>
		<id>qdm</id>
		<sort>22</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/orim</url>
		<columnName>ORIM Mapping</columnName>
		<title>Ontological RIM Mapping</title>
		<id>orim</id>
		<sort>23</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/w5</url>
    <link>http://hl7.org/fhir/fivews.html</link>
		<columnName>...don't use...</columnName>
		<title>W5 Mapping</title>
		<id>w5</id>
		<sort>24</sort>
	</space>
	<space>
		<url>http://hl7.org/fhir/logical</url>
    <link></link>
		<columnName>Logical Mapping</columnName>
		<title>Logical Mapping</title>
		<id>logical</id>
		<sort>25</sort>
		<publish>true</publish>
    <preamble>
			<p>
      These mappings map logical models to their conceptual equivalents in FHIR. One example of their use is to map from the CDA and V2 coded data types to CodeableConcept and Coding so that the validator can validate them on a terminology server
     </p>
		</preamble>
	</space>
	<space>
		<url>http://hl7.org/fhir/auditevent</url>
    <link>http://hl7.org/fhir/auditevent.html</link>
		<columnName>Auditevent Mapping</columnName>
		<title>FHIR AuditEvent Mapping</title>
		<id>fhirauditevent</id>
		<sort>26</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/provenance</url>
    <link>http://hl7.org/fhir/provenance.html</link>
		<columnName>Provenance Mapping</columnName>
		<title>FHIR Provenance Mapping</title>
		<id>fhirprovenance</id>
		<sort>27</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/qidam</url>
		<link>http://www.hl7.org/implement/standards/product_brief.cfm?product_id=378</link>
		<columnName>QIDAM Mapping</columnName>
		<title>Mapping to Quality Improvement Domain Analysis Model</title>
		<id>qidam</id>
		<sort>28</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://cap.org/ecc</url>
		<link>https://www.cap.org/laboratory-improvement/proficiency-testing/cap-ecc</link>
		<columnName>CAP Code</columnName>
		<title>Equivalent CAP Code</title>
		<id>cap</id>
		<sort>29</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://fda.gov/UDI</url>
		<link>http://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/UniqueDeviceIdentification/default.htm</link>
		<columnName>UDI Mapping</columnName>
		<title>UDI Mapping</title>
		<id>udi</id>
		<preamble>
			<p>UDI is a unique numeric or alphanumeric code that consists of two parts:
			 (1) a device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device, and (2)
		a production identifier (PI), a conditional, variable portion of a UDI that identifies one or more of the following when included on the label of a device:
		 (2a) the lot or batch number within which a device was manufactured; (2b) the serial number of a specific device; (2c) the expiration date of a specific device; (2d) the date a specific device was manufactured; (2e) the distinct identification code required by §1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device.
	</p>
		</preamble>
		<sort>30</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/object-implementation</url>
		<columnName>Object Impl</columnName>
		<title>Object Implementation Information</title>
		<id>objimpl</id>
		<sort>31</sort>
	</space>
	<space>
		<url>http://github.com/MDMI/ReferentIndexContent</url>
		<link>http://github.com/MDMI/ReferentIndexContent</link>
		<columnName>MDMI Referent</columnName>
		<title>MDMI Referent Index Mapping</title>
		<id>mdmi</id>
		<sort>32</sort>
    <publish>true</publish>
	</space>
	<space>
		<url>http://ncpdp.org/SCRIPT10_6</url>
		<link>http://www.ncpdp.org/NCPDP/media/pdf/NCPDPEprescribing101.pdf</link>
		<columnName>SCRIPT 10.6 Mapping</columnName>
		<title>Mapping to NCPDP SCRIPT 10.6</title>
		<id>script10.6</id>
		<sort>33</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://clinicaltrials.gov</url>
		<link>http://clinicaltrials.gov</link>
		<columnName>clinicaltrials.gov Mapping</columnName>
		<title>ClinicalTrials.gov Mapping</title>
		<id>clinicaltrials-gov</id>
		<sort>35</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/rr</url>
		<columnName>R3-RR-Mapping</columnName>
		<title>R3-ReferalRequest Mapping</title>
		<id>rr-map</id>
		<sort>36</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://www.hl7.org/v3/PORX_RM020070UV</url>
		<link>http://www.hl7.org/documentcenter/private/standards/v3/edition_web/domains/uvrx/uvrx_MedicationDispenseEvent.html#PORX_RM020070UV</link>
		<columnName>V3 Dispense Mapping</columnName>
		<title>V3 Pharmacy Dispense RMIM</title>
		<id>rx-dispense-rmim</id>
		<sort>37</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>https://bridgmodel.nci.nih.gov</url>
		<link>https://bridgmodel.nci.nih.gov/download-model/bridg-releases/release-51/release-package</link>
		<columnName>BRIDG 5.1 Mapping</columnName>
		<title>BRIDG 5.1 Mapping</title>
		<id>BRIDG5.1</id>
		<sort>38</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/composition</url>
    <link>http://hl7.org/fhir/composition.html</link>
		<columnName>Composition Mapping</columnName>
		<title>FHIR Composition</title>
		<id>fhircomposition</id>
		<sort>39</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/documentreference</url>
    <link>http://hl7.org/fhir/documentreference.html</link>
		<columnName>DocumentReference Mapping</columnName>
		<title>FHIR DocumentReference</title>
		<id>fhirdocumentreference</id>
		<sort>40</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>https://www.iso.org/obp/ui/#iso:std:iso:11615</url>
		<link>https://www.iso.org/obp/ui/#iso:std:iso:11615</link>
		<columnName>IDMP Mapping</columnName>
		<title>IDMP Mapping</title>
		<id>idmp</id>
		<sort>41</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>urn:iso:std:iso:11073:10201</url>
		<link>https://standards.ieee.org/standard/11073-10201-2018.html</link>
		<columnName>ISO/IEEE 11073-10201</columnName>
		<title>ISO/IEEE 11073-10201</title>
		<id>DIM</id>
		<sort>42</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>urn:iso:std:iso:11073:10207</url>
		<link>https://standards.ieee.org/standard/11073-10207-2019.html</link>
		<columnName>ISO/IEEE 11073-10207</columnName>
		<title>ISO/IEEE 11073-10207</title>
		<id>BICEPS</id>
		<sort>43</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>http://hl7.org/fhir/consent</url>
    <link>http://hl7.org/fhir/consent.html</link>
		<columnName>Consent Mapping</columnName>
		<title>FHIR Consent Mapping</title>
		<id>fhirconsent</id>
		<sort>44</sort>
		<publish>true</publish>
	</space>
	<space>
	    <url>https://www.isbt128.org/uri/</url>
		<link>https://www.isbt128.org/uri/</link>
		<columnName>ISBT 128 Code</columnName>
		<title>ISBT 128 Codes</title>
		<id>ISBT128Code</id>
		<sort>51</sort>
		<publish>true</publish>
	</space>
	<space>
		<url>https://www.iso.org/obp/ui/#iso:std:iso:11238</url>
		<link>https://www.iso.org/obp/ui/#iso:std:iso:11238</link>
		<columnName>IDMP Mapping (Substance)</columnName>
		<title>IDMP Mapping (Substance)</title>
		<id>idmp-substance</id>
		<sort>52</sort>
		<publish>true</publish>
	</space>
</mappingSpaces>
