Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU
Extensions for Using Data Elements from FHIR STU3 in FHIR R4 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "ConceptMap",
"id" : "R3-DiagnosticReport-element-map-to-R4",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R3-DiagnosticReport-element-map-to-R4</b></p><a name=\"R3-DiagnosticReport-element-map-to-R4\"> </a><a name=\"hcR3-DiagnosticReport-element-map-to-R4\"> </a><p>Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DiagnosticReport|3.0.2</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=\"http://hl7.org/fhir/R5/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=\"http://hl7.org/fhir/R5/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`.\nAsserting 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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.</td></tr><tr><td>DiagnosticReport.language (language)</td><td><a href=\"http://hl7.org/fhir/R5/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`.\nLanguage 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=\"http://hl7.org/fhir/R5/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`.\nContained resources do not have 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 "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.</td></tr><tr><td>DiagnosticReport.contained (contained)</td><td><a href=\"http://hl7.org/fhir/R5/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`.\nThis 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.</td></tr><tr><td>DiagnosticReport.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/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`.\nUsually assigned by the Information System of the diagnostic service provider (filler id).</td></tr><tr><td>DiagnosticReport.basedOn (basedOn)</td><td><a href=\"http://hl7.org/fhir/R5/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 `SourceIsNarrowerThanTarget`.\nNote: 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=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.status</td><td>Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `Equivalent`.\nThis is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn.</td></tr><tr><td>DiagnosticReport.category (category)</td><td><a href=\"http://hl7.org/fhir/R5/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 `SourceIsNarrowerThanTarget`.\nThe 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=\"http://hl7.org/fhir/R5/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=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.subject</td><td>Element `DiagnosticReport.subject` is mapped to FHIR R4 element `DiagnosticReport.subject` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.context (context)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>DiagnosticReport.encounter</td><td>Element `DiagnosticReport.context` is mapped to FHIR R4 element `DiagnosticReport.encounter` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.context` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.context` with unmapped reference targets: EpisodeOfCare.\nThis 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 or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests).</td></tr><tr><td>DiagnosticReport.effective[x] (effective[x])</td><td><a href=\"http://hl7.org/fhir/R5/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`.\nThe target context `DiagnosticReport.effective[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DiagnosticReport`.\nIf 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=\"http://hl7.org/fhir/R5/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`.\nMay 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=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>DiagnosticReport.performer</td><td>Element `DiagnosticReport.performer` is mapped to FHIR R4 element `DiagnosticReport.performer` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.performer.actor (actor)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.performer</td><td>Element `DiagnosticReport.performer.actor` is mapped to FHIR R4 element `DiagnosticReport.performer` as `RelatedTo`.\nThis is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report.</td></tr><tr><td>DiagnosticReport.specimen (specimen)</td><td><a href=\"http://hl7.org/fhir/R5/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`.\nIf 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=\"http://hl7.org/fhir/R5/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`.</td></tr><tr><td>DiagnosticReport.imagingStudy (imagingStudy)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>DiagnosticReport.imagingStudy</td><td>Element `DiagnosticReport.imagingStudy` is mapped to FHIR R4 element `DiagnosticReport.imagingStudy` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.imagingStudy` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.imagingStudy` with unmapped reference targets: ImagingManifest.\nImagingStudy and ImageManifest and the image element are somewhat overlapping - typically, the list of image references in the image 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><tr><td>DiagnosticReport.image (image)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>DiagnosticReport.media</td><td>Element `DiagnosticReport.image` is mapped to FHIR R4 element `DiagnosticReport.media` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.image.comment (comment)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.media.comment</td><td>Element `DiagnosticReport.image.comment` is mapped to FHIR R4 element `DiagnosticReport.media.comment` as `Equivalent`.\nThe comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion.</td></tr><tr><td>DiagnosticReport.image.link (link)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.media.link</td><td>Element `DiagnosticReport.image.link` is mapped to FHIR R4 element `DiagnosticReport.media.link` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.conclusion (conclusion)</td><td><a href=\"http://hl7.org/fhir/R5/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.codedDiagnosis (codedDiagnosis)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DiagnosticReport.conclusionCode</td><td>Element `DiagnosticReport.codedDiagnosis` is mapped to FHIR R4 element `DiagnosticReport.conclusionCode` as `Equivalent`.</td></tr><tr><td>DiagnosticReport.presentedForm (presentedForm)</td><td><a href=\"http://hl7.org/fhir/R5/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`.\n"application/pdf" 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|3.0.2</code> to <a href=\"StructureDefinition-ext-R3-DiagnosticReport.per.role.html\">STU3: Type of performer (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.performer.role (role)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>Extension (STU3: Type of performer (new))</td><td>Element `DiagnosticReport.performer.role` has a context of DiagnosticReport.performer based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.performer.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).</td></tr></table></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "fhir"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 0,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R3-DiagnosticReport-element-map-to-R4",
"version" : "0.1.0",
"name" : "R3DiagnosticReportElementMapToR4",
"title" : "Cross-version mapping for FHIR STU3 DiagnosticReport to FHIR R4 DiagnosticReport",
"status" : "active",
"experimental" : false,
"date" : "2026-03-17T16:03:23.6268251-05:00",
"contact" : [
{
"name" : "FHIR Infrastructure",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/fiwg"
}
]
}
],
"description" : "This ConceptMap represents cross-version mappings for elements from a FHIR STU3 DiagnosticReport to FHIR R4.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"sourceCanonical" : "http://hl7.org/fhir/3.0",
"targetUri" : "http://hl7.org/fhir/4.0",
"group" : [
{
"source" : "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion" : "3.0.2",
"target" : "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"targetVersion" : "4.0.1",
"element" : [
{
"code" : "DiagnosticReport.meta",
"display" : "meta",
"target" : [
{
"code" : "DiagnosticReport.meta",
"display" : "DiagnosticReport.meta",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.meta` is mapped to FHIR R4 element `DiagnosticReport.meta` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.implicitRules",
"display" : "implicitRules",
"target" : [
{
"code" : "DiagnosticReport.implicitRules",
"display" : "DiagnosticReport.implicitRules",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.implicitRules` is mapped to FHIR R4 element `DiagnosticReport.implicitRules` as `Equivalent`.\nAsserting 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. \n\nThis element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation."
}
]
},
{
"code" : "DiagnosticReport.language",
"display" : "language",
"target" : [
{
"code" : "DiagnosticReport.language",
"display" : "DiagnosticReport.language",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.language` is mapped to FHIR R4 element `DiagnosticReport.language` as `Equivalent`.\nLanguage 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)."
}
]
},
{
"code" : "DiagnosticReport.text",
"display" : "text",
"target" : [
{
"code" : "DiagnosticReport.text",
"display" : "DiagnosticReport.text",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.text` is mapped to FHIR R4 element `DiagnosticReport.text` as `Equivalent`.\nContained resources do not have 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 \"text blob\" or where text is additionally entered raw or narrated and encoded in formation is added later."
}
]
},
{
"code" : "DiagnosticReport.contained",
"display" : "contained",
"target" : [
{
"code" : "DiagnosticReport.contained",
"display" : "DiagnosticReport.contained",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.contained` is mapped to FHIR R4 element `DiagnosticReport.contained` as `Equivalent`.\nThis 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."
}
]
},
{
"code" : "DiagnosticReport.identifier",
"display" : "identifier",
"target" : [
{
"code" : "DiagnosticReport.identifier",
"display" : "DiagnosticReport.identifier",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.identifier` is mapped to FHIR R4 element `DiagnosticReport.identifier` as `Equivalent`.\nUsually assigned by the Information System of the diagnostic service provider (filler id)."
}
]
},
{
"code" : "DiagnosticReport.basedOn",
"display" : "basedOn",
"target" : [
{
"code" : "DiagnosticReport.basedOn",
"display" : "DiagnosticReport.basedOn",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.basedOn` is mapped to FHIR R4 element `DiagnosticReport.basedOn` as `SourceIsNarrowerThanTarget`.\nNote: 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."
}
]
},
{
"code" : "DiagnosticReport.status",
"display" : "status",
"target" : [
{
"code" : "DiagnosticReport.status",
"display" : "DiagnosticReport.status",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `Equivalent`.\nThis is labeled as \"Is Modifier\" because applications need to take appropriate action if a report is withdrawn."
}
]
},
{
"code" : "DiagnosticReport.category",
"display" : "category",
"target" : [
{
"code" : "DiagnosticReport.category",
"display" : "DiagnosticReport.category",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.category` is mapped to FHIR R4 element `DiagnosticReport.category` as `SourceIsNarrowerThanTarget`.\nThe 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."
}
]
},
{
"code" : "DiagnosticReport.code",
"display" : "code",
"target" : [
{
"code" : "DiagnosticReport.code",
"display" : "DiagnosticReport.code",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.code` is mapped to FHIR R4 element `DiagnosticReport.code` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.subject",
"display" : "subject",
"target" : [
{
"code" : "DiagnosticReport.subject",
"display" : "DiagnosticReport.subject",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.subject` is mapped to FHIR R4 element `DiagnosticReport.subject` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.context",
"display" : "context",
"target" : [
{
"code" : "DiagnosticReport.encounter",
"display" : "DiagnosticReport.encounter",
"equivalence" : "wider",
"comment" : "Element `DiagnosticReport.context` is mapped to FHIR R4 element `DiagnosticReport.encounter` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.context` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.context` with unmapped reference targets: EpisodeOfCare.\nThis 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 or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests)."
}
]
},
{
"code" : "DiagnosticReport.effective[x]",
"display" : "effective[x]",
"target" : [
{
"code" : "DiagnosticReport.effective[x]",
"display" : "DiagnosticReport.effective[x]",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.effective[x]` is mapped to FHIR R4 element `DiagnosticReport.effective[x]` as `Equivalent`.\nThe target context `DiagnosticReport.effective[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DiagnosticReport`.\nIf 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."
}
]
},
{
"code" : "DiagnosticReport.issued",
"display" : "issued",
"target" : [
{
"code" : "DiagnosticReport.issued",
"display" : "DiagnosticReport.issued",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.issued` is mapped to FHIR R4 element `DiagnosticReport.issued` as `Equivalent`.\nMay 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."
}
]
},
{
"code" : "DiagnosticReport.performer",
"display" : "performer",
"target" : [
{
"code" : "DiagnosticReport.performer",
"display" : "DiagnosticReport.performer",
"equivalence" : "wider",
"comment" : "Element `DiagnosticReport.performer` is mapped to FHIR R4 element `DiagnosticReport.performer` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.performer.actor",
"display" : "actor",
"target" : [
{
"code" : "DiagnosticReport.performer",
"display" : "DiagnosticReport.performer",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.performer.actor` is mapped to FHIR R4 element `DiagnosticReport.performer` as `RelatedTo`.\nThis is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report."
}
]
},
{
"code" : "DiagnosticReport.specimen",
"display" : "specimen",
"target" : [
{
"code" : "DiagnosticReport.specimen",
"display" : "DiagnosticReport.specimen",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.specimen` is mapped to FHIR R4 element `DiagnosticReport.specimen` as `Equivalent`.\nIf 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."
}
]
},
{
"code" : "DiagnosticReport.result",
"display" : "result",
"target" : [
{
"code" : "DiagnosticReport.result",
"display" : "DiagnosticReport.result",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.result` is mapped to FHIR R4 element `DiagnosticReport.result` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.imagingStudy",
"display" : "imagingStudy",
"target" : [
{
"code" : "DiagnosticReport.imagingStudy",
"display" : "DiagnosticReport.imagingStudy",
"equivalence" : "wider",
"comment" : "Element `DiagnosticReport.imagingStudy` is mapped to FHIR R4 element `DiagnosticReport.imagingStudy` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.imagingStudy` do not cover the following types based on type expansion: display, identifier, reference.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.imagingStudy` with unmapped reference targets: ImagingManifest.\nImagingStudy and ImageManifest and the image element are somewhat overlapping - typically, the list of image references in the image 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."
}
]
},
{
"code" : "DiagnosticReport.image",
"display" : "image",
"target" : [
{
"code" : "DiagnosticReport.media",
"display" : "DiagnosticReport.media",
"equivalence" : "wider",
"comment" : "Element `DiagnosticReport.image` is mapped to FHIR R4 element `DiagnosticReport.media` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.image.comment",
"display" : "comment",
"target" : [
{
"code" : "DiagnosticReport.media.comment",
"display" : "DiagnosticReport.media.comment",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.image.comment` is mapped to FHIR R4 element `DiagnosticReport.media.comment` as `Equivalent`.\nThe comment should be displayed with the image. It would be common for the report to include additional discussion of the image contents in other sections such as the conclusion."
}
]
},
{
"code" : "DiagnosticReport.image.link",
"display" : "link",
"target" : [
{
"code" : "DiagnosticReport.media.link",
"display" : "DiagnosticReport.media.link",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.image.link` is mapped to FHIR R4 element `DiagnosticReport.media.link` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.conclusion",
"display" : "conclusion",
"target" : [
{
"code" : "DiagnosticReport.conclusion",
"display" : "DiagnosticReport.conclusion",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.conclusion` is mapped to FHIR R4 element `DiagnosticReport.conclusion` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.codedDiagnosis",
"display" : "codedDiagnosis",
"target" : [
{
"code" : "DiagnosticReport.conclusionCode",
"display" : "DiagnosticReport.conclusionCode",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.codedDiagnosis` is mapped to FHIR R4 element `DiagnosticReport.conclusionCode` as `Equivalent`."
}
]
},
{
"code" : "DiagnosticReport.presentedForm",
"display" : "presentedForm",
"target" : [
{
"code" : "DiagnosticReport.presentedForm",
"display" : "DiagnosticReport.presentedForm",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.presentedForm` is mapped to FHIR R4 element `DiagnosticReport.presentedForm` as `Equivalent`.\n\"application/pdf\" is recommended as the most reliable and interoperable in this context."
}
]
}
]
},
{
"source" : "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion" : "3.0.2",
"target" : "http://hl7.org/fhir/3.0/StructureDefinition/extension-DiagnosticReport.performer.role",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "DiagnosticReport.performer.role",
"display" : "role",
"target" : [
{
"code" : "Extension",
"equivalence" : "equivalent",
"comment" : "Element `DiagnosticReport.performer.role` has a context of DiagnosticReport.performer based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.performer.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element)."
}
]
}
]
}
]
}
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r3.r4#0.1.0 based on FHIR 4.0.1. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change