Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: R5DiagnosticReportElementMapToR4 - XML Representation

Raw xml | Download

<ConceptMap xmlns="http://hl7.org/fhir">
  <id value="R5-DiagnosticReport-element-map-to-R4"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R5-DiagnosticReport-element-map-to-R4</b></p><a name="R5-DiagnosticReport-element-map-to-R4"> </a><a name="hcR5-DiagnosticReport-element-map-to-R4"> </a><p>Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="http://hl7.org/fhir/R4/diagnosticreport.html">DiagnosticReportversion: 4.0.1)</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>DiagnosticReport.meta (meta)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.meta</td><td>Element `DiagnosticReport.meta` is mapped to FHIR R4 element `DiagnosticReport.meta` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.implicitRules (implicitRules)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.implicitRules</td><td>Element `DiagnosticReport.implicitRules` is mapped to FHIR R4 element `DiagnosticReport.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.</td></tr><tr><td>DiagnosticReport.language (language)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.language</td><td>Element `DiagnosticReport.language` is mapped to FHIR R4 element `DiagnosticReport.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).</td></tr><tr><td>DiagnosticReport.text (text)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.text</td><td>Element `DiagnosticReport.text` is mapped to FHIR R4 element `DiagnosticReport.text` as `Equivalent`.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later.</td></tr><tr><td>DiagnosticReport.contained (contained)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.contained</td><td>Element `DiagnosticReport.contained` is mapped to FHIR R4 element `DiagnosticReport.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.</td></tr><tr><td>DiagnosticReport.identifier (identifier)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.identifier</td><td>Element `DiagnosticReport.identifier` is mapped to FHIR R4 element `DiagnosticReport.identifier` as `Equivalent`.
Usually assigned by the Information System of the diagnostic service provider (filler id).</td></tr><tr><td>DiagnosticReport.basedOn (basedOn)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.basedOn</td><td>Element `DiagnosticReport.basedOn` is mapped to FHIR R4 element `DiagnosticReport.basedOn` as `Equivalent`.
Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports.</td></tr><tr><td>DiagnosticReport.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>DiagnosticReport.status</td><td>Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `RelatedTo`.
The mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.
The target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier.</td></tr><tr><td>DiagnosticReport.category (category)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.category</td><td>Element `DiagnosticReport.category` is mapped to FHIR R4 element `DiagnosticReport.category` as `Equivalent`.
Multiple categories are allowed using various categorization schemes.   The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code.</td></tr><tr><td>DiagnosticReport.code (code)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.code</td><td>Element `DiagnosticReport.code` is mapped to FHIR R4 element `DiagnosticReport.code` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.subject (subject)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>DiagnosticReport.subject</td><td>Element `DiagnosticReport.subject` is mapped to FHIR R4 element `DiagnosticReport.subject` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.subject` with unmapped reference targets: BiologicallyDerivedProduct, Medication, Organization, Practitioner, Substance.</td></tr><tr><td>DiagnosticReport.encounter (encounter)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.encounter</td><td>Element `DiagnosticReport.encounter` is mapped to FHIR R4 element `DiagnosticReport.encounter` as `Equivalent`.
This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter  but still be tied to the context of the encounter  (e.g. pre-admission laboratory tests).</td></tr><tr><td>DiagnosticReport.effective[x] (effective[x])</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.effective[x]</td><td>Element `DiagnosticReport.effective[x]` is mapped to FHIR R4 element `DiagnosticReport.effective[x]` as `Equivalent`.
The target context `DiagnosticReport.effective[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DiagnosticReport`.
If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic.</td></tr><tr><td>DiagnosticReport.issued (issued)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.issued</td><td>Element `DiagnosticReport.issued` is mapped to FHIR R4 element `DiagnosticReport.issued` as `Equivalent`.
May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report.</td></tr><tr><td>DiagnosticReport.performer (performer)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.performer</td><td>Element `DiagnosticReport.performer` is mapped to FHIR R4 element `DiagnosticReport.performer` as `Equivalent`.
This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report.</td></tr><tr><td>DiagnosticReport.resultsInterpreter (resultsInterpreter)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.resultsInterpreter</td><td>Element `DiagnosticReport.resultsInterpreter` is mapped to FHIR R4 element `DiagnosticReport.resultsInterpreter` as `Equivalent`.
Might not be the same entity that takes responsibility for the clinical report.</td></tr><tr><td>DiagnosticReport.specimen (specimen)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.specimen</td><td>Element `DiagnosticReport.specimen` is mapped to FHIR R4 element `DiagnosticReport.specimen` as `Equivalent`.
If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group.</td></tr><tr><td>DiagnosticReport.result (result)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.result</td><td>Element `DiagnosticReport.result` is mapped to FHIR R4 element `DiagnosticReport.result` as `Equivalent`.
Observations can contain observations.</td></tr><tr><td>DiagnosticReport.media (media)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>DiagnosticReport.media</td><td>Element `DiagnosticReport.media` is mapped to FHIR R4 element `DiagnosticReport.media` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.media.comment (comment)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.media.comment</td><td>Element `DiagnosticReport.media.comment` is mapped to FHIR R4 element `DiagnosticReport.media.comment` as `Equivalent`.
The comment should be displayed with the image or data. It would be common for the report to include additional discussion of the image or data contents or in other sections such as the conclusion.</td></tr><tr><td>DiagnosticReport.media.link (link)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>DiagnosticReport.media.link</td><td>Element `DiagnosticReport.media.link` is mapped to FHIR R4 element `DiagnosticReport.media.link` as `SourceIsBroaderThanTarget`.
The mappings for `DiagnosticReport.media.link` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.media.link` with unmapped reference targets: DocumentReference.</td></tr><tr><td>DiagnosticReport.conclusion (conclusion)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.conclusion</td><td>Element `DiagnosticReport.conclusion` is mapped to FHIR R4 element `DiagnosticReport.conclusion` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.conclusionCode (conclusionCode)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.conclusionCode</td><td>Element `DiagnosticReport.conclusionCode` is mapped to FHIR R4 element `DiagnosticReport.conclusionCode` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.presentedForm (presentedForm)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>DiagnosticReport.presentedForm</td><td>Element `DiagnosticReport.presentedForm` is mapped to FHIR R4 element `DiagnosticReport.presentedForm` as `Equivalent`.
&quot;application/pdf&quot; is recommended as the most reliable and interoperable in this context.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="StructureDefinition-ext-R5-DiagnosticReport.status.html">R5: registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown additional codesversion: 0.1.0)</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>DiagnosticReport.status (status)</td><td><a href="CodeSystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R5: registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown additional codes)</td><td>Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `RelatedTo`.
The mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.
The target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="StructureDefinition-ext-R5-DiagnosticReport.note.html">R5: Comments about the diagnostic report (new)version: 0.1.0)</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>DiagnosticReport.note (note)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Comments about the diagnostic report (new))</td><td>Element `DiagnosticReport.note` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
May include general statements about the diagnostic report, or statements about significant, unexpected or unreliable results values contained within the diagnostic report, or information about its source when relevant to its interpretation.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="StructureDefinition-ext-R5-DiagnosticReport.study.html">R5: Reference to full details of an analysis associated with the diagnostic report (new)version: 0.1.0)</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>DiagnosticReport.study (study)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Reference to full details of an analysis associated with the diagnostic report (new))</td><td>Element `DiagnosticReport.study` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.study` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
For laboratory-type studies like GenomeStudy, type resources will be used for tracking additional metadata and workflow aspects of complex studies. ImagingStudy and the media element are somewhat overlapping - typically, the list of image references in the media element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided.</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="StructureDefinition-ext-R5-DiagnosticReport.supportingInfo.html">R5: Additional information supporting the diagnostic report (new)version: 0.1.0)</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>DiagnosticReport.supportingInfo (supportingInfo)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Additional information supporting the diagnostic report (new))</td><td>Element `DiagnosticReport.supportingInfo` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>DiagnosticReport.supportingInfo.type (type)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:type (R5: Supporting information role code (new))</td><td>Element `DiagnosticReport.supportingInfo.type` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.
Element `DiagnosticReport.supportingInfo.type` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr><tr><td>DiagnosticReport.supportingInfo.reference (reference)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension.extension:reference (R5: Supporting information reference (new))</td><td>Element `DiagnosticReport.supportingInfo.reference` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.
Element `DiagnosticReport.supportingInfo.reference` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 6 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0</code> to <a href="StructureDefinition-ext-R5-DiagnosticReport.composition.html">R5: Reference to a Composition resource for the DiagnosticReport structure (new)version: 0.1.0)</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>DiagnosticReport.composition (composition)</td><td><a href="CodeSystem-concept-map-relationship.html#wider" title="wider">maps to wider concept</a></td><td>Extension (R5: Reference to a Composition resource for the DiagnosticReport structure (new))</td><td>Element `DiagnosticReport.composition` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.composition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report.</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="fhir"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="0">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"/>
      </extension>
    </valueInteger>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r4"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/xver/ConceptMap/R5-DiagnosticReport-element-map-to-R4"/>
  <version value="0.1.0"/>
  <name value="R5DiagnosticReportElementMapToR4"/>
  <title
         value="Cross-version mapping for FHIR R5 DiagnosticReport to FHIR R4 DiagnosticReport"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-03-17T16:04:45.1635541-05:00"/>
  <contact>
    <name value="FHIR Infrastructure"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/fiwg"/>
    </telecom>
  </contact>
  <description
               value="This ConceptMap represents cross-version mappings for elements from a FHIR R5 DiagnosticReport to FHIR R4."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <sourceCanonical value="http://hl7.org/fhir/5.0"/>
  <targetUri value="http://hl7.org/fhir/4.0"/>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <targetVersion value="4.0.1"/>
    <element>
      <code value="DiagnosticReport.meta"/>
      <display value="meta"/>
      <target>
        <code value="DiagnosticReport.meta"/>
        <display value="DiagnosticReport.meta"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.meta` is mapped to FHIR R4 element `DiagnosticReport.meta` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.implicitRules"/>
      <display value="implicitRules"/>
      <target>
        <code value="DiagnosticReport.implicitRules"/>
        <display value="DiagnosticReport.implicitRules"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.implicitRules` is mapped to FHIR R4 element `DiagnosticReport.implicitRules` as `Equivalent`.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.language"/>
      <display value="language"/>
      <target>
        <code value="DiagnosticReport.language"/>
        <display value="DiagnosticReport.language"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.language` is mapped to FHIR R4 element `DiagnosticReport.language` as `Equivalent`.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies  to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute)."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.text"/>
      <display value="text"/>
      <target>
        <code value="DiagnosticReport.text"/>
        <display value="DiagnosticReport.text"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.text` is mapped to FHIR R4 element `DiagnosticReport.text` as `Equivalent`.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied).  This may be necessary for data from legacy systems where information is captured as a &quot;text blob&quot; or where text is additionally entered raw or narrated and encoded information is added later."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.contained"/>
      <display value="contained"/>
      <target>
        <code value="DiagnosticReport.contained"/>
        <display value="DiagnosticReport.contained"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.contained` is mapped to FHIR R4 element `DiagnosticReport.contained` as `Equivalent`.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.identifier"/>
      <display value="identifier"/>
      <target>
        <code value="DiagnosticReport.identifier"/>
        <display value="DiagnosticReport.identifier"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.identifier` is mapped to FHIR R4 element `DiagnosticReport.identifier` as `Equivalent`.
Usually assigned by the Information System of the diagnostic service provider (filler id)."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.basedOn"/>
      <display value="basedOn"/>
      <target>
        <code value="DiagnosticReport.basedOn"/>
        <display value="DiagnosticReport.basedOn"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.basedOn` is mapped to FHIR R4 element `DiagnosticReport.basedOn` as `Equivalent`.
Note: Usually there is one test request for each result, however in some circumstances multiple test requests may be represented using a single test result resource. Note that there are also cases where one request leads to multiple reports."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.status"/>
      <display value="status"/>
      <target>
        <code value="DiagnosticReport.status"/>
        <display value="DiagnosticReport.status"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `RelatedTo`.
The mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.
The target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.category"/>
      <display value="category"/>
      <target>
        <code value="DiagnosticReport.category"/>
        <display value="DiagnosticReport.category"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.category` is mapped to FHIR R4 element `DiagnosticReport.category` as `Equivalent`.
Multiple categories are allowed using various categorization schemes.   The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in DiagnosticReport.code."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.code"/>
      <display value="code"/>
      <target>
        <code value="DiagnosticReport.code"/>
        <display value="DiagnosticReport.code"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.code` is mapped to FHIR R4 element `DiagnosticReport.code` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.subject"/>
      <display value="subject"/>
      <target>
        <code value="DiagnosticReport.subject"/>
        <display value="DiagnosticReport.subject"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.subject` is mapped to FHIR R4 element `DiagnosticReport.subject` as `SourceIsBroaderThanTarget`.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.subject` with unmapped reference targets: BiologicallyDerivedProduct, Medication, Organization, Practitioner, Substance."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.encounter"/>
      <display value="encounter"/>
      <target>
        <code value="DiagnosticReport.encounter"/>
        <display value="DiagnosticReport.encounter"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.encounter` is mapped to FHIR R4 element `DiagnosticReport.encounter` as `Equivalent`.
This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter  but still be tied to the context of the encounter  (e.g. pre-admission laboratory tests)."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.effective[x]"/>
      <display value="effective[x]"/>
      <target>
        <code value="DiagnosticReport.effective[x]"/>
        <display value="DiagnosticReport.effective[x]"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.effective[x]` is mapped to FHIR R4 element `DiagnosticReport.effective[x]` as `Equivalent`.
The target context `DiagnosticReport.effective[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DiagnosticReport`.
If the diagnostic procedure was performed on the patient, this is the time it was performed. If there are specimens, the diagnostically relevant time can be derived from the specimen collection times, but the specimen information is not always available, and the exact relationship between the specimens and the diagnostically relevant time is not always automatic."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.issued"/>
      <display value="issued"/>
      <target>
        <code value="DiagnosticReport.issued"/>
        <display value="DiagnosticReport.issued"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.issued` is mapped to FHIR R4 element `DiagnosticReport.issued` as `Equivalent`.
May be different from the update time of the resource itself, because that is the status of the record (potentially a secondary copy), not the actual release time of the report."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.performer"/>
      <display value="performer"/>
      <target>
        <code value="DiagnosticReport.performer"/>
        <display value="DiagnosticReport.performer"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.performer` is mapped to FHIR R4 element `DiagnosticReport.performer` as `Equivalent`.
This is not necessarily the source of the atomic data items or the entity that interpreted the results. It is the entity that takes responsibility for the clinical report."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.resultsInterpreter"/>
      <display value="resultsInterpreter"/>
      <target>
        <code value="DiagnosticReport.resultsInterpreter"/>
        <display value="DiagnosticReport.resultsInterpreter"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.resultsInterpreter` is mapped to FHIR R4 element `DiagnosticReport.resultsInterpreter` as `Equivalent`.
Might not be the same entity that takes responsibility for the clinical report."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.specimen"/>
      <display value="specimen"/>
      <target>
        <code value="DiagnosticReport.specimen"/>
        <display value="DiagnosticReport.specimen"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.specimen` is mapped to FHIR R4 element `DiagnosticReport.specimen` as `Equivalent`.
If the specimen is sufficiently specified with a code in the test result name, then this additional data may be redundant. If there are multiple specimens, these may be represented per observation or group."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.result"/>
      <display value="result"/>
      <target>
        <code value="DiagnosticReport.result"/>
        <display value="DiagnosticReport.result"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.result` is mapped to FHIR R4 element `DiagnosticReport.result` as `Equivalent`.
Observations can contain observations."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.media"/>
      <display value="media"/>
      <target>
        <code value="DiagnosticReport.media"/>
        <display value="DiagnosticReport.media"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.media` is mapped to FHIR R4 element `DiagnosticReport.media` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.media.comment"/>
      <display value="comment"/>
      <target>
        <code value="DiagnosticReport.media.comment"/>
        <display value="DiagnosticReport.media.comment"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.media.comment` is mapped to FHIR R4 element `DiagnosticReport.media.comment` as `Equivalent`.
The comment should be displayed with the image or data. It would be common for the report to include additional discussion of the image or data contents or in other sections such as the conclusion."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.media.link"/>
      <display value="link"/>
      <target>
        <code value="DiagnosticReport.media.link"/>
        <display value="DiagnosticReport.media.link"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.media.link` is mapped to FHIR R4 element `DiagnosticReport.media.link` as `SourceIsBroaderThanTarget`.
The mappings for `DiagnosticReport.media.link` do not cover the following types based on type expansion: display, identifier, reference, type.
The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.media.link` with unmapped reference targets: DocumentReference."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.conclusion"/>
      <display value="conclusion"/>
      <target>
        <code value="DiagnosticReport.conclusion"/>
        <display value="DiagnosticReport.conclusion"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.conclusion` is mapped to FHIR R4 element `DiagnosticReport.conclusion` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.conclusionCode"/>
      <display value="conclusionCode"/>
      <target>
        <code value="DiagnosticReport.conclusionCode"/>
        <display value="DiagnosticReport.conclusionCode"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.conclusionCode` is mapped to FHIR R4 element `DiagnosticReport.conclusionCode` as `Equivalent`."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.presentedForm"/>
      <display value="presentedForm"/>
      <target>
        <code value="DiagnosticReport.presentedForm"/>
        <display value="DiagnosticReport.presentedForm"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.presentedForm` is mapped to FHIR R4 element `DiagnosticReport.presentedForm` as `Equivalent`.
&quot;application/pdf&quot; is recommended as the most reliable and interoperable in this context."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target
            value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.status"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="DiagnosticReport.status"/>
      <display value="status"/>
      <target>
        <code value="Extension"/>
        <equivalence value="equivalent"/>
        <comment
                 value="Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `RelatedTo`.
The mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.
The target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target
            value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.note"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="DiagnosticReport.note"/>
      <display value="note"/>
      <target>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.note` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
May include general statements about the diagnostic report, or statements about significant, unexpected or unreliable results values contained within the diagnostic report, or information about its source when relevant to its interpretation."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target
            value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.study"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="DiagnosticReport.study"/>
      <display value="study"/>
      <target>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.study` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.study` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
For laboratory-type studies like GenomeStudy, type resources will be used for tracking additional metadata and workflow aspects of complex studies. ImagingStudy and the media element are somewhat overlapping - typically, the list of image references in the media element will also be found in one of the imaging study resources. However, each caters to different types of displays for different types of purposes. Neither, either, or both may be provided."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target
            value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.supportingInfo"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="DiagnosticReport.supportingInfo"/>
      <display value="supportingInfo"/>
      <target>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.supportingInfo` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.supportingInfo.type"/>
      <display value="type"/>
      <target>
        <code value="Extension.extension:type"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.supportingInfo.type` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.
Element `DiagnosticReport.supportingInfo.type` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
    <element>
      <code value="DiagnosticReport.supportingInfo.reference"/>
      <display value="reference"/>
      <target>
        <code value="Extension.extension:reference"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.supportingInfo.reference` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.
Element `DiagnosticReport.supportingInfo.reference` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.supportingInfo.reference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."/>
      </target>
    </element>
  </group>
  <group>
    <source value="http://hl7.org/fhir/StructureDefinition/DiagnosticReport"/>
    <sourceVersion value="5.0.0"/>
    <target
            value="http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition"/>
    <targetVersion value="0.1.0"/>
    <element>
      <code value="DiagnosticReport.composition"/>
      <display value="composition"/>
      <target>
        <code value="Extension"/>
        <equivalence value="wider"/>
        <comment
                 value="Element `DiagnosticReport.composition` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.
Element `DiagnosticReport.composition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
The Composition provides structure to the content of the DiagnosticReport (and only contains contents referenced in the DiagnosticReport) - e.g., to order the sections of an anatomic pathology structured report."/>
      </target>
    </element>
  </group>
</ConceptMap>