FHIR IG analytics| Package | hl7.fhir.uv.xver-r5.r3 |
| Resource Type | ConceptMap |
| Id | ConceptMap-R5-DiagnosticReport-element-map-to-R3.json |
| FHIR Version | R3 |
| Source | http://hl7.org/fhir/uv/xver-r5.r3/0.1.0/ConceptMap-R5-DiagnosticReport-element-map-to-R3.html |
| URL | http://hl7.org/fhir/uv/xver/ConceptMap/R5-DiagnosticReport-element-map-to-R3 |
| Version | 0.1.0 |
| Status | active |
| Date | 2026-03-17T16:05:15.6156867-05:00 |
| Name | R5DiagnosticReportElementMapToR3 |
| Title | Cross-version mapping for FHIR R5 DiagnosticReport to FHIR STU3 DiagnosticReport |
| Realm | uv |
| Authority | hl7 |
| Description | This ConceptMap represents cross-version mappings for elements from a FHIR R5 DiagnosticReport to FHIR STU3. |
No resources found
| StructureDefinition | ||
| eng.fhir.profile.dev#0.0.7-beta | extension-DiagnosticReport.composition | diagnosticReport-compositioR5 |
| fhir.r4.ukcore.stu3.currentbuild#0.28.0-pre-release | extension-DiagnosticReport.note | Extension UK Core Diagnostic Report Note |
| hl7.fhir.uv.xver-r5.r3#0.1.0 | extension-DiagnosticReport.resultsInterpreter | R5: Primary result interpreter (new) |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-DiagnosticReport.status | Cross-version Extension for R5.DiagnosticReport.status for use in FHIR R4 |
| hl7.fhir.uv.xver-r5.r4.r4#0.0.1-snapshot-2 | extension-DiagnosticReport.study | Cross-version Extension for R5.DiagnosticReport.study for use in FHIR R4 |
| fhir.r4.ukcore.stu3.currentbuild#0.28.0-pre-release | extension-DiagnosticReport.supportingInfo | Extension UK Core Diagnostic Report Supporting Info |
Note: links and images are rebased to the (stated) source
Generated Narrative: ConceptMap R5-DiagnosticReport-element-map-to-R3
Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/3.0
Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to http://hl7.org/fhir/StructureDefinition/DiagnosticReport|3.0.2
| Source Concept Details | Relationship | Target Concept Details | Comment | ||
| Codes from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 | Codes from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|3.0.2 | ||||
| DiagnosticReport.meta | meta | is equivalent to | DiagnosticReport.meta | DiagnosticReport.meta | Element `DiagnosticReport.meta` is mapped to FHIR STU3 element `DiagnosticReport.meta` as `Equivalent`. |
| DiagnosticReport.implicitRules | implicitRules | is equivalent to | DiagnosticReport.implicitRules | DiagnosticReport.implicitRules | Element `DiagnosticReport.implicitRules` is mapped to FHIR STU3 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. |
| DiagnosticReport.language | language | is equivalent to | DiagnosticReport.language | DiagnosticReport.language | Element `DiagnosticReport.language` is mapped to FHIR STU3 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). |
| DiagnosticReport.text | text | is equivalent to | DiagnosticReport.text | DiagnosticReport.text | Element `DiagnosticReport.text` is mapped to FHIR STU3 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 "text blob" or where text is additionally entered raw or narrated and encoded information is added later. |
| DiagnosticReport.contained | contained | is equivalent to | DiagnosticReport.contained | DiagnosticReport.contained | Element `DiagnosticReport.contained` is mapped to FHIR STU3 element `DiagnosticReport.contained` as `SourceIsBroaderThanTarget`. 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. |
| DiagnosticReport.identifier | identifier | is equivalent to | DiagnosticReport.identifier | DiagnosticReport.identifier | Element `DiagnosticReport.identifier` is mapped to FHIR STU3 element `DiagnosticReport.identifier` as `Equivalent`. Usually assigned by the Information System of the diagnostic service provider (filler id). |
| DiagnosticReport.basedOn | basedOn | maps to wider concept | DiagnosticReport.basedOn | DiagnosticReport.basedOn | Element `DiagnosticReport.basedOn` is mapped to FHIR STU3 element `DiagnosticReport.basedOn` as `SourceIsBroaderThanTarget`. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.basedOn` with unmapped reference targets: CarePlan, ImmunizationRecommendation, MedicationRequest, NutritionOrder, ServiceRequest. 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. |
| DiagnosticReport.status | status | maps to wider concept | DiagnosticReport.status | DiagnosticReport.status | Element `DiagnosticReport.status` is mapped to FHIR STU3 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. |
| DiagnosticReport.category | category | is equivalent to | DiagnosticReport.category | DiagnosticReport.category | Element `DiagnosticReport.category` is mapped to FHIR STU3 element `DiagnosticReport.category` as `SourceIsBroaderThanTarget`. 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. |
| DiagnosticReport.code | code | is equivalent to | DiagnosticReport.code | DiagnosticReport.code | Element `DiagnosticReport.code` is mapped to FHIR STU3 element `DiagnosticReport.code` as `Equivalent`. |
| DiagnosticReport.subject | subject | maps to wider concept | DiagnosticReport.subject | DiagnosticReport.subject | Element `DiagnosticReport.subject` is mapped to FHIR STU3 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, Device, Group, Location, Medication, Organization, Patient, Practitioner, Substance. |
| DiagnosticReport.encounter | encounter | maps to wider concept | DiagnosticReport.context | DiagnosticReport.context | Element `DiagnosticReport.encounter` is mapped to FHIR STU3 element `DiagnosticReport.context` as `SourceIsBroaderThanTarget`. The mappings for `DiagnosticReport.encounter` 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.encounter` with unmapped reference targets: Encounter. 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). |
| DiagnosticReport.effective[x] | effective[x] | is equivalent to | DiagnosticReport.effective[x] | DiagnosticReport.effective[x] | Element `DiagnosticReport.effective[x]` is mapped to FHIR STU3 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. |
| DiagnosticReport.issued | issued | is equivalent to | DiagnosticReport.issued | DiagnosticReport.issued | Element `DiagnosticReport.issued` is mapped to FHIR STU3 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. |
| DiagnosticReport.performer | performer | is equivalent to | DiagnosticReport.performer | DiagnosticReport.performer | Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer` as `Equivalent`. Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer.actor` as `RelatedTo`. 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. |
| is related to | DiagnosticReport.performer.actor | DiagnosticReport.performer.actor | Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer` as `Equivalent`. Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer.actor` as `RelatedTo`. 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. | ||
| DiagnosticReport.specimen | specimen | maps to wider concept | DiagnosticReport.specimen | DiagnosticReport.specimen | Element `DiagnosticReport.specimen` is mapped to FHIR STU3 element `DiagnosticReport.specimen` as `SourceIsBroaderThanTarget`. The mappings for `DiagnosticReport.specimen` 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.specimen` with unmapped reference targets: Specimen. 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. |
| DiagnosticReport.result | result | maps to wider concept | DiagnosticReport.result | DiagnosticReport.result | Element `DiagnosticReport.result` is mapped to FHIR STU3 element `DiagnosticReport.result` as `SourceIsBroaderThanTarget`. The mappings for `DiagnosticReport.result` 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.result` with unmapped reference targets: Observation. Observations can contain observations. |
| DiagnosticReport.media | media | maps to wider concept | DiagnosticReport.image | DiagnosticReport.image | Element `DiagnosticReport.media` is mapped to FHIR STU3 element `DiagnosticReport.image` as `Equivalent`. |
| DiagnosticReport.media.comment | comment | is equivalent to | DiagnosticReport.image.comment | DiagnosticReport.image.comment | Element `DiagnosticReport.media.comment` is mapped to FHIR STU3 element `DiagnosticReport.image.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. |
| DiagnosticReport.media.link | link | maps to wider concept | DiagnosticReport.image.link | DiagnosticReport.image.link | Element `DiagnosticReport.media.link` is mapped to FHIR STU3 element `DiagnosticReport.image.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. |
| DiagnosticReport.conclusion | conclusion | is equivalent to | DiagnosticReport.conclusion | DiagnosticReport.conclusion | Element `DiagnosticReport.conclusion` is mapped to FHIR STU3 element `DiagnosticReport.conclusion` as `Equivalent`. |
| DiagnosticReport.conclusionCode | conclusionCode | is equivalent to | DiagnosticReport.codedDiagnosis | DiagnosticReport.codedDiagnosis | Element `DiagnosticReport.conclusionCode` is mapped to FHIR STU3 element `DiagnosticReport.codedDiagnosis` as `Equivalent`. |
| DiagnosticReport.presentedForm | presentedForm | is equivalent to | DiagnosticReport.presentedForm | DiagnosticReport.presentedForm | Element `DiagnosticReport.presentedForm` is mapped to FHIR STU3 element `DiagnosticReport.presentedForm` as `Equivalent`. "application/pdf" is recommended as the most reliable and interoperable in this context. |
Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown additional codesversion: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.status (status) | is equivalent to | Extension (R5: registered | partial | preliminary | modified | final | amended | corrected | appended | cancelled | entered-in-error | unknown additional codes) | Element `DiagnosticReport.status` is mapped to FHIR STU3 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. |
Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: Primary result interpreter (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.resultsInterpreter (resultsInterpreter) | is equivalent to | Extension (R5: Primary result interpreter (new)) | Element `DiagnosticReport.resultsInterpreter` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`. Element `DiagnosticReport.resultsInterpreter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Might not be the same entity that takes responsibility for the clinical report. |
Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: Comments about the diagnostic report (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.note (note) | maps to wider concept | Extension (R5: Comments about the diagnostic report (new)) | 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 STU3. 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. |
Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: Reference to full details of an analysis associated with the diagnostic report (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.study (study) | maps to wider concept | Extension (R5: Reference to full details of an analysis associated with the diagnostic report (new)) | 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 STU3. 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. |
Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: Additional information supporting the diagnostic report (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.supportingInfo (supportingInfo) | maps to wider concept | Extension (R5: Additional information supporting the diagnostic report (new)) | 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 STU3. Typically, this is because the element has been added (is a new element). |
| DiagnosticReport.supportingInfo.type (type) | maps to wider concept | Extension.extension:type (R5: Supporting information role code (new)) | 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 STU3. Typically, this is because the element has been added (is a new element). |
| DiagnosticReport.supportingInfo.reference (reference) | maps to wider concept | Extension.extension:reference (R5: Supporting information reference (new)) | 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 STU3. Typically, this is because the element has been added (is a new element). |
Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|5.0.0 to R5: Reference to a Composition resource for the DiagnosticReport structure (new)version: 0.1.0)
| Source Code | Relationship | Target Code | Comment |
| DiagnosticReport.composition (composition) | maps to wider concept | Extension (R5: Reference to a Composition resource for the DiagnosticReport structure (new)) | 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 STU3. 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. |
{
"resourceType": "ConceptMap",
"id": "R5-DiagnosticReport-element-map-to-R3",
"text": {
"status": "generated",
"div": "<!-- snip (see above) -->"
},
"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",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
},
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode": "trial-use",
"_valueCode": {
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueUri": "http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r5.r3"
}
]
}
}
],
"url": "http://hl7.org/fhir/uv/xver/ConceptMap/R5-DiagnosticReport-element-map-to-R3",
"version": "0.1.0",
"name": "R5DiagnosticReportElementMapToR3",
"title": "Cross-version mapping for FHIR R5 DiagnosticReport to FHIR STU3 DiagnosticReport",
"status": "active",
"experimental": false,
"date": "2026-03-17T16:05:15.6156867-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 R5 DiagnosticReport to FHIR STU3.",
"jurisdiction": [
{
"coding": [
{
"system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code": "001",
"display": "World"
}
]
}
],
"sourceUri": "http://hl7.org/fhir/5.0",
"targetUri": "http://hl7.org/fhir/3.0",
"group": [
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"targetVersion": "3.0.2",
"element": [
{
"code": "DiagnosticReport.meta",
"display": "meta",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.meta",
"display": "DiagnosticReport.meta",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.meta` is mapped to FHIR STU3 element `DiagnosticReport.meta` as `Equivalent`."
}
]
},
{
"code": "DiagnosticReport.implicitRules",
"display": "implicitRules",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.implicitRules",
"display": "DiagnosticReport.implicitRules",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.implicitRules` is mapped to FHIR STU3 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. 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."
}
]
},
{
"code": "DiagnosticReport.language",
"display": "language",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.language",
"display": "DiagnosticReport.language",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.language` is mapped to FHIR STU3 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": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.text",
"display": "DiagnosticReport.text",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.text` is mapped to FHIR STU3 element `DiagnosticReport.text` as `Equivalent`.\nContained 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 \"text blob\" or where text is additionally entered raw or narrated and encoded information is added later."
}
]
},
{
"code": "DiagnosticReport.contained",
"display": "contained",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.contained",
"display": "DiagnosticReport.contained",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.contained` is mapped to FHIR STU3 element `DiagnosticReport.contained` as `SourceIsBroaderThanTarget`.\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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels."
}
]
},
{
"code": "DiagnosticReport.identifier",
"display": "identifier",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.identifier",
"display": "DiagnosticReport.identifier",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.identifier` is mapped to FHIR STU3 element `DiagnosticReport.identifier` as `Equivalent`.\nUsually assigned by the Information System of the diagnostic service provider (filler id)."
}
]
},
{
"code": "DiagnosticReport.basedOn",
"display": "basedOn",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.basedOn",
"display": "DiagnosticReport.basedOn",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.basedOn` is mapped to FHIR STU3 element `DiagnosticReport.basedOn` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.basedOn` with unmapped reference targets: CarePlan, ImmunizationRecommendation, MedicationRequest, NutritionOrder, ServiceRequest.\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": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.status",
"display": "DiagnosticReport.status",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.status` is mapped to FHIR STU3 element `DiagnosticReport.status` as `RelatedTo`.\nThe mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nThe target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier."
}
]
},
{
"code": "DiagnosticReport.category",
"display": "category",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.category",
"display": "DiagnosticReport.category",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.category` is mapped to FHIR STU3 element `DiagnosticReport.category` as `SourceIsBroaderThanTarget`.\nMultiple 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."
}
]
},
{
"code": "DiagnosticReport.code",
"display": "code",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.code",
"display": "DiagnosticReport.code",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.code` is mapped to FHIR STU3 element `DiagnosticReport.code` as `Equivalent`."
}
]
},
{
"code": "DiagnosticReport.subject",
"display": "subject",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.subject",
"display": "DiagnosticReport.subject",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.subject` is mapped to FHIR STU3 element `DiagnosticReport.subject` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.subject` with unmapped reference targets: BiologicallyDerivedProduct, Device, Group, Location, Medication, Organization, Patient, Practitioner, Substance."
}
]
},
{
"code": "DiagnosticReport.encounter",
"display": "encounter",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.context",
"display": "DiagnosticReport.context",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.encounter` is mapped to FHIR STU3 element `DiagnosticReport.context` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.encounter` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.encounter` with unmapped reference targets: Encounter.\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 but still be tied to the context of the encounter (e.g. pre-admission laboratory tests)."
}
]
},
{
"code": "DiagnosticReport.effective[x]",
"display": "effective[x]",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.effective[x]",
"display": "DiagnosticReport.effective[x]",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.effective[x]` is mapped to FHIR STU3 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": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.issued",
"display": "DiagnosticReport.issued",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.issued` is mapped to FHIR STU3 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": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.performer",
"display": "DiagnosticReport.performer",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer` as `Equivalent`.\nElement `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer.actor` as `RelatedTo`.\nThis 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."
},
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "relatedto"
}
],
"code": "DiagnosticReport.performer.actor",
"display": "DiagnosticReport.performer.actor",
"equivalence": "relatedto",
"comment": "Element `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer` as `Equivalent`.\nElement `DiagnosticReport.performer` is mapped to FHIR STU3 element `DiagnosticReport.performer.actor` as `RelatedTo`.\nThis 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."
}
]
},
{
"code": "DiagnosticReport.specimen",
"display": "specimen",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.specimen",
"display": "DiagnosticReport.specimen",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.specimen` is mapped to FHIR STU3 element `DiagnosticReport.specimen` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.specimen` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.specimen` with unmapped reference targets: Specimen.\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": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.result",
"display": "DiagnosticReport.result",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.result` is mapped to FHIR STU3 element `DiagnosticReport.result` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.result` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.result` with unmapped reference targets: Observation.\nObservations can contain observations."
}
]
},
{
"code": "DiagnosticReport.media",
"display": "media",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.image",
"display": "DiagnosticReport.image",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.media` is mapped to FHIR STU3 element `DiagnosticReport.image` as `Equivalent`."
}
]
},
{
"code": "DiagnosticReport.media.comment",
"display": "comment",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.image.comment",
"display": "DiagnosticReport.image.comment",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.media.comment` is mapped to FHIR STU3 element `DiagnosticReport.image.comment` as `Equivalent`.\nThe 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."
}
]
},
{
"code": "DiagnosticReport.media.link",
"display": "link",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "DiagnosticReport.image.link",
"display": "DiagnosticReport.image.link",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.media.link` is mapped to FHIR STU3 element `DiagnosticReport.image.link` as `SourceIsBroaderThanTarget`.\nThe mappings for `DiagnosticReport.media.link` do not cover the following types based on type expansion: display, identifier, reference, type.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `DiagnosticReport.media.link` with unmapped reference targets: DocumentReference."
}
]
},
{
"code": "DiagnosticReport.conclusion",
"display": "conclusion",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.conclusion",
"display": "DiagnosticReport.conclusion",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.conclusion` is mapped to FHIR STU3 element `DiagnosticReport.conclusion` as `Equivalent`."
}
]
},
{
"code": "DiagnosticReport.conclusionCode",
"display": "conclusionCode",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.codedDiagnosis",
"display": "DiagnosticReport.codedDiagnosis",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.conclusionCode` is mapped to FHIR STU3 element `DiagnosticReport.codedDiagnosis` as `Equivalent`."
}
]
},
{
"code": "DiagnosticReport.presentedForm",
"display": "presentedForm",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "DiagnosticReport.presentedForm",
"display": "DiagnosticReport.presentedForm",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.presentedForm` is mapped to FHIR STU3 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": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.status",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.status",
"display": "status",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Extension",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.status` is mapped to FHIR STU3 element `DiagnosticReport.status` as `RelatedTo`.\nThe mappings for `DiagnosticReport.status` do not allow expression of the necessary codes, per the bindings on the source and target.\nThe target context `DiagnosticReport.status` is a modifier element, so this extension does not need to be defined as a modifier."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.resultsInterpreter",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.resultsInterpreter",
"display": "resultsInterpreter",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "equivalent"
}
],
"code": "Extension",
"equivalence": "equivalent",
"comment": "Element `DiagnosticReport.resultsInterpreter` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.resultsInterpreter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nMight not be the same entity that takes responsibility for the clinical report."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.note",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.note",
"display": "note",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.note` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nMay 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.study",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.study",
"display": "study",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.study` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.study` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nFor 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."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.supportingInfo",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.supportingInfo",
"display": "supportingInfo",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.supportingInfo` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.supportingInfo` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "DiagnosticReport.supportingInfo.type",
"display": "type",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:type",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.supportingInfo.type` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.\nElement `DiagnosticReport.supportingInfo.type` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.supportingInfo.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
},
{
"code": "DiagnosticReport.supportingInfo.reference",
"display": "reference",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension.extension:reference",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.supportingInfo.reference` is part of an existing definition because parent element `DiagnosticReport.supportingInfo` requires a cross-version extension.\nElement `DiagnosticReport.supportingInfo.reference` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.supportingInfo.reference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
},
{
"source": "http://hl7.org/fhir/StructureDefinition/DiagnosticReport",
"sourceVersion": "5.0.0",
"target": "http://hl7.org/fhir/5.0/StructureDefinition/extension-DiagnosticReport.composition",
"targetVersion": "0.1.0",
"element": [
{
"code": "DiagnosticReport.composition",
"display": "composition",
"target": [
{
"modifierExtension": [
{
"url": "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode": "wider"
}
],
"code": "Extension",
"equivalence": "wider",
"comment": "Element `DiagnosticReport.composition` has a context of DiagnosticReport based on following the parent source element upwards and mapping to `DiagnosticReport`.\nElement `DiagnosticReport.composition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe 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."
}
]
}
]
}
]
}