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

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

ConceptMap: R4DiagnosticReportElementMapToR3

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

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

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


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

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|4.0.1Codes from http://hl7.org/fhir/StructureDefinition/DiagnosticReport|3.0.2
DiagnosticReport.metametais equivalent toDiagnosticReport.metaDiagnosticReport.metaElement `DiagnosticReport.meta` is mapped to FHIR STU3 element `DiagnosticReport.meta` as `Equivalent`.
DiagnosticReport.implicitRulesimplicitRulesis equivalent toDiagnosticReport.implicitRulesDiagnosticReport.implicitRulesElement `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 it's narrative along with other profiles, value sets, etc.
DiagnosticReport.languagelanguageis equivalent toDiagnosticReport.languageDiagnosticReport.languageElement `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.texttextis equivalent toDiagnosticReport.textDiagnosticReport.textElement `DiagnosticReport.text` is mapped to FHIR STU3 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 information is added later.
DiagnosticReport.containedcontainedis equivalent toDiagnosticReport.containedDiagnosticReport.containedElement `DiagnosticReport.contained` is mapped to FHIR STU3 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.
DiagnosticReport.identifieridentifieris equivalent toDiagnosticReport.identifierDiagnosticReport.identifierElement `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.basedOnbasedOnmaps to wider conceptDiagnosticReport.basedOnDiagnosticReport.basedOnElement `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 R4 element `DiagnosticReport.basedOn` with unmapped reference targets: 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.statusstatusis equivalent toDiagnosticReport.statusDiagnosticReport.statusElement `DiagnosticReport.status` is mapped to FHIR STU3 element `DiagnosticReport.status` as `Equivalent`.
DiagnosticReport.categorycategoryis equivalent toDiagnosticReport.categoryDiagnosticReport.categoryElement `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.codecodeis equivalent toDiagnosticReport.codeDiagnosticReport.codeElement `DiagnosticReport.code` is mapped to FHIR STU3 element `DiagnosticReport.code` as `Equivalent`.
DiagnosticReport.subjectsubjectis equivalent toDiagnosticReport.subjectDiagnosticReport.subjectElement `DiagnosticReport.subject` is mapped to FHIR STU3 element `DiagnosticReport.subject` as `Equivalent`.
DiagnosticReport.encounterencounteris equivalent toDiagnosticReport.contextDiagnosticReport.contextElement `DiagnosticReport.encounter` is mapped to FHIR STU3 element `DiagnosticReport.context` 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).
DiagnosticReport.effective[x]effective[x]is equivalent toDiagnosticReport.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.issuedissuedis equivalent toDiagnosticReport.issuedDiagnosticReport.issuedElement `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.performerperformeris equivalent toDiagnosticReport.performerDiagnosticReport.performerElement `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 toDiagnosticReport.performer.actorDiagnosticReport.performer.actorElement `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.specimenspecimenis equivalent toDiagnosticReport.specimenDiagnosticReport.specimenElement `DiagnosticReport.specimen` is mapped to FHIR STU3 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.resultresultis equivalent toDiagnosticReport.resultDiagnosticReport.resultElement `DiagnosticReport.result` is mapped to FHIR STU3 element `DiagnosticReport.result` as `Equivalent`. Observations can contain observations.
DiagnosticReport.imagingStudyimagingStudyis equivalent toDiagnosticReport.imagingStudyDiagnosticReport.imagingStudyElement `DiagnosticReport.imagingStudy` is mapped to FHIR STU3 element `DiagnosticReport.imagingStudy` as `Equivalent`. ImagingStudy 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.mediamediamaps to wider conceptDiagnosticReport.imageDiagnosticReport.imageElement `DiagnosticReport.media` is mapped to FHIR STU3 element `DiagnosticReport.image` as `Equivalent`.
DiagnosticReport.media.commentcommentis equivalent toDiagnosticReport.image.commentDiagnosticReport.image.commentElement `DiagnosticReport.media.comment` is mapped to FHIR STU3 element `DiagnosticReport.image.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.media.linklinkis equivalent toDiagnosticReport.image.linkDiagnosticReport.image.linkElement `DiagnosticReport.media.link` is mapped to FHIR STU3 element `DiagnosticReport.image.link` as `Equivalent`.
DiagnosticReport.conclusionconclusionis equivalent toDiagnosticReport.conclusionDiagnosticReport.conclusionElement `DiagnosticReport.conclusion` is mapped to FHIR STU3 element `DiagnosticReport.conclusion` as `Equivalent`.
DiagnosticReport.conclusionCodeconclusionCodeis equivalent toDiagnosticReport.codedDiagnosisDiagnosticReport.codedDiagnosisElement `DiagnosticReport.conclusionCode` is mapped to FHIR STU3 element `DiagnosticReport.codedDiagnosis` as `Equivalent`.
DiagnosticReport.presentedFormpresentedFormis equivalent toDiagnosticReport.presentedFormDiagnosticReport.presentedFormElement `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|4.0.1 to R4: Primary result interpreter (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
DiagnosticReport.resultsInterpreter (resultsInterpreter)maps to wider conceptExtension (R4: 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.