Extensions for Using Data Elements from FHIR STU3 in FHIR R4
0.1.0 - STU International flag

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

ConceptMap: R3DiagnosticReportElementMapToR4

Official URL: http://hl7.org/fhir/uv/xver/ConceptMap/R3-DiagnosticReport-element-map-to-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R3DiagnosticReportElementMapToR4

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 DiagnosticReport to FHIR R4.

Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|3.0.2 to DiagnosticReportversion: 4.0.1)

Source CodeRelationshipTarget CodeComment
DiagnosticReport.meta (meta)is equivalent toDiagnosticReport.metaElement `DiagnosticReport.meta` is mapped to FHIR R4 element `DiagnosticReport.meta` as `Equivalent`.
DiagnosticReport.implicitRules (implicitRules)is equivalent toDiagnosticReport.implicitRulesElement `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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
DiagnosticReport.language (language)is equivalent toDiagnosticReport.languageElement `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).
DiagnosticReport.text (text)is equivalent toDiagnosticReport.textElement `DiagnosticReport.text` is mapped to FHIR R4 element `DiagnosticReport.text` as `Equivalent`. Contained 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.
DiagnosticReport.contained (contained)is equivalent toDiagnosticReport.containedElement `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.
DiagnosticReport.identifier (identifier)is equivalent toDiagnosticReport.identifierElement `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).
DiagnosticReport.basedOn (basedOn)is equivalent toDiagnosticReport.basedOnElement `DiagnosticReport.basedOn` is mapped to FHIR R4 element `DiagnosticReport.basedOn` as `SourceIsNarrowerThanTarget`. 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)is equivalent toDiagnosticReport.statusElement `DiagnosticReport.status` is mapped to FHIR R4 element `DiagnosticReport.status` as `Equivalent`. This is labeled as "Is Modifier" because applications need to take appropriate action if a report is withdrawn.
DiagnosticReport.category (category)is equivalent toDiagnosticReport.categoryElement `DiagnosticReport.category` is mapped to FHIR R4 element `DiagnosticReport.category` as `SourceIsNarrowerThanTarget`. 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 toDiagnosticReport.codeElement `DiagnosticReport.code` is mapped to FHIR R4 element `DiagnosticReport.code` as `Equivalent`.
DiagnosticReport.subject (subject)is equivalent toDiagnosticReport.subjectElement `DiagnosticReport.subject` is mapped to FHIR R4 element `DiagnosticReport.subject` as `Equivalent`.
DiagnosticReport.context (context)maps to wider conceptDiagnosticReport.encounterElement `DiagnosticReport.context` is mapped to FHIR R4 element `DiagnosticReport.encounter` as `SourceIsBroaderThanTarget`. The mappings for `DiagnosticReport.context` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.context` with unmapped reference targets: EpisodeOfCare. 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 or episode but still be tied to the context of the encounter or episode (e.g. pre-admission lab tests).
DiagnosticReport.effective[x] (effective[x])is equivalent toDiagnosticReport.effective[x]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.
DiagnosticReport.issued (issued)is equivalent toDiagnosticReport.issuedElement `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.
DiagnosticReport.performer (performer)maps to wider conceptDiagnosticReport.performerElement `DiagnosticReport.performer` is mapped to FHIR R4 element `DiagnosticReport.performer` as `Equivalent`.
DiagnosticReport.performer.actor (actor)is equivalent toDiagnosticReport.performerElement `DiagnosticReport.performer.actor` is mapped to FHIR R4 element `DiagnosticReport.performer` as `RelatedTo`. This is not necessarily the source of the atomic data items. It is the entity that takes responsibility for the clinical report.
DiagnosticReport.specimen (specimen)is equivalent toDiagnosticReport.specimenElement `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.
DiagnosticReport.result (result)is equivalent toDiagnosticReport.resultElement `DiagnosticReport.result` is mapped to FHIR R4 element `DiagnosticReport.result` as `Equivalent`.
DiagnosticReport.imagingStudy (imagingStudy)maps to wider conceptDiagnosticReport.imagingStudyElement `DiagnosticReport.imagingStudy` is mapped to FHIR R4 element `DiagnosticReport.imagingStudy` as `SourceIsBroaderThanTarget`. The mappings for `DiagnosticReport.imagingStudy` do not cover the following types based on type expansion: display, identifier, reference. The standard extension `alternate-reference` has been mapped as the representation of FHIR STU3 element `DiagnosticReport.imagingStudy` with unmapped reference targets: ImagingManifest. ImagingStudy 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.
DiagnosticReport.image (image)maps to wider conceptDiagnosticReport.mediaElement `DiagnosticReport.image` is mapped to FHIR R4 element `DiagnosticReport.media` as `Equivalent`.
DiagnosticReport.image.comment (comment)is equivalent toDiagnosticReport.media.commentElement `DiagnosticReport.image.comment` is mapped to FHIR R4 element `DiagnosticReport.media.comment` as `Equivalent`. The 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.
DiagnosticReport.image.link (link)is equivalent toDiagnosticReport.media.linkElement `DiagnosticReport.image.link` is mapped to FHIR R4 element `DiagnosticReport.media.link` as `Equivalent`.
DiagnosticReport.conclusion (conclusion)is equivalent toDiagnosticReport.conclusionElement `DiagnosticReport.conclusion` is mapped to FHIR R4 element `DiagnosticReport.conclusion` as `Equivalent`.
DiagnosticReport.codedDiagnosis (codedDiagnosis)is equivalent toDiagnosticReport.conclusionCodeElement `DiagnosticReport.codedDiagnosis` is mapped to FHIR R4 element `DiagnosticReport.conclusionCode` as `Equivalent`.
DiagnosticReport.presentedForm (presentedForm)is equivalent toDiagnosticReport.presentedFormElement `DiagnosticReport.presentedForm` is mapped to FHIR R4 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|3.0.2 to STU3: Type of performer (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DiagnosticReport.performer.role (role)is equivalent toExtension (STU3: Type of performer (new))Element `DiagnosticReport.performer.role` has a context of DiagnosticReport.performer based on following the parent source element upwards and mapping to `DiagnosticReport`. Element `DiagnosticReport.performer.role` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).