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

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

ConceptMap: R3TestReportElementMapToR4B

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

This ConceptMap represents cross-version mappings for elements from a FHIR STU3 TestReport to FHIR R4B.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/TestReport|3.0.2 to TestReportversion: 4.3.0)

Source CodeRelationshipTarget CodeComment
TestReport.meta (meta)maps to wider conceptTestReport.metaElement `TestReport.meta` is mapped to FHIR R4B element `TestReport.meta` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.meta` do not cover the following types: Meta. The mappings for `TestReport.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
TestReport.implicitRules (implicitRules)is equivalent toTestReport.implicitRulesElement `TestReport.implicitRules` is mapped to FHIR R4B element `TestReport.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.
TestReport.language (language)is equivalent toTestReport.languageElement `TestReport.language` is mapped to FHIR R4B element `TestReport.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).
TestReport.text (text)maps to wider conceptTestReport.textElement `TestReport.text` is mapped to FHIR R4B element `TestReport.text` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.text` do not cover the following types: Narrative. The mappings for `TestReport.text` do not cover the following types based on type expansion: div, status. 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.
TestReport.contained (contained)is equivalent toTestReport.containedElement `TestReport.contained` is mapped to FHIR R4B element `TestReport.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.
TestReport.identifier (identifier)maps to wider conceptTestReport.identifierElement `TestReport.identifier` is mapped to FHIR R4B element `TestReport.identifier` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.identifier` do not cover the following types: Identifier. The mappings for `TestReport.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.
TestReport.name (name)is equivalent toTestReport.nameElement `TestReport.name` is mapped to FHIR R4B element `TestReport.name` as `Equivalent`. Not expected to be globally unique.
TestReport.status (status)is equivalent toTestReport.statusElement `TestReport.status` is mapped to FHIR R4B element `TestReport.status` as `Equivalent`. The status represents where the execution is currently within the test script execution life cycle. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
TestReport.testScript (testScript)maps to wider conceptTestReport.testScriptElement `TestReport.testScript` is mapped to FHIR R4B element `TestReport.testScript` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.testScript` 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 `TestReport.testScript` with unmapped reference targets: TestScript.
TestReport.result (result)is equivalent toTestReport.resultElement `TestReport.result` is mapped to FHIR R4B element `TestReport.result` as `Equivalent`. The pass and fail result represents a completed test script execution. The pending result represents a test script execution that has not yet started or is currently in progress.
TestReport.score (score)is equivalent toTestReport.scoreElement `TestReport.score` is mapped to FHIR R4B element `TestReport.score` as `Equivalent`.
TestReport.tester (tester)is equivalent toTestReport.testerElement `TestReport.tester` is mapped to FHIR R4B element `TestReport.tester` as `Equivalent`. Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.
TestReport.issued (issued)is equivalent toTestReport.issuedElement `TestReport.issued` is mapped to FHIR R4B element `TestReport.issued` as `Equivalent`. Additional specific dates may be added as extensions.
TestReport.participant (participant)maps to wider conceptTestReport.participantElement `TestReport.participant` is mapped to FHIR R4B element `TestReport.participant` as `Equivalent`.
TestReport.participant.type (type)is equivalent toTestReport.participant.typeElement `TestReport.participant.type` is mapped to FHIR R4B element `TestReport.participant.type` as `Equivalent`.
TestReport.participant.uri (uri)is equivalent toTestReport.participant.uriElement `TestReport.participant.uri` is mapped to FHIR R4B element `TestReport.participant.uri` as `Equivalent`.
TestReport.participant.display (display)is equivalent toTestReport.participant.displayElement `TestReport.participant.display` is mapped to FHIR R4B element `TestReport.participant.display` as `Equivalent`.
TestReport.setup (setup)maps to wider conceptTestReport.setupElement `TestReport.setup` is mapped to FHIR R4B element `TestReport.setup` as `Equivalent`.
TestReport.setup.action (action)maps to wider conceptTestReport.setup.actionElement `TestReport.setup.action` is mapped to FHIR R4B element `TestReport.setup.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
TestReport.setup.action.operation (operation)maps to wider conceptTestReport.setup.action.operationElement `TestReport.setup.action.operation` is mapped to FHIR R4B element `TestReport.setup.action.operation` as `Equivalent`.
TestReport.setup.action.operation.result (result)is equivalent toTestReport.setup.action.operation.resultElement `TestReport.setup.action.operation.result` is mapped to FHIR R4B element `TestReport.setup.action.operation.result` as `Equivalent`.
TestReport.setup.action.operation.message (message)is equivalent toTestReport.setup.action.operation.messageElement `TestReport.setup.action.operation.message` is mapped to FHIR R4B element `TestReport.setup.action.operation.message` as `Equivalent`.
TestReport.setup.action.operation.detail (detail)is equivalent toTestReport.setup.action.operation.detailElement `TestReport.setup.action.operation.detail` is mapped to FHIR R4B element `TestReport.setup.action.operation.detail` as `Equivalent`.
TestReport.setup.action.assert (assert)maps to wider conceptTestReport.setup.action.assertElement `TestReport.setup.action.assert` is mapped to FHIR R4B element `TestReport.setup.action.assert` as `Equivalent`.
TestReport.setup.action.assert.result (result)is equivalent toTestReport.setup.action.assert.resultElement `TestReport.setup.action.assert.result` is mapped to FHIR R4B element `TestReport.setup.action.assert.result` as `Equivalent`.
TestReport.setup.action.assert.message (message)is equivalent toTestReport.setup.action.assert.messageElement `TestReport.setup.action.assert.message` is mapped to FHIR R4B element `TestReport.setup.action.assert.message` as `Equivalent`.
TestReport.setup.action.assert.detail (detail)is equivalent toTestReport.setup.action.assert.detailElement `TestReport.setup.action.assert.detail` is mapped to FHIR R4B element `TestReport.setup.action.assert.detail` as `Equivalent`.
TestReport.test (test)maps to wider conceptTestReport.testElement `TestReport.test` is mapped to FHIR R4B element `TestReport.test` as `Equivalent`.
TestReport.test.name (name)is equivalent toTestReport.test.nameElement `TestReport.test.name` is mapped to FHIR R4B element `TestReport.test.name` as `Equivalent`.
TestReport.test.description (description)is equivalent toTestReport.test.descriptionElement `TestReport.test.description` is mapped to FHIR R4B element `TestReport.test.description` as `Equivalent`.
TestReport.test.action (action)maps to wider conceptTestReport.test.actionElement `TestReport.test.action` is mapped to FHIR R4B element `TestReport.test.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
TestReport.test.action.operation (operation)is equivalent toTestReport.test.action.operationElement `TestReport.test.action.operation` is mapped to FHIR R4B element `TestReport.test.action.operation` as `Equivalent`.
TestReport.test.action.assert (assert)is equivalent toTestReport.test.action.assertElement `TestReport.test.action.assert` is mapped to FHIR R4B element `TestReport.test.action.assert` as `Equivalent`.
TestReport.teardown (teardown)maps to wider conceptTestReport.teardownElement `TestReport.teardown` is mapped to FHIR R4B element `TestReport.teardown` as `Equivalent`.
TestReport.teardown.action (action)maps to wider conceptTestReport.teardown.actionElement `TestReport.teardown.action` is mapped to FHIR R4B element `TestReport.teardown.action` as `Equivalent`. An action should contain either an operation or an assertion but not both. It can contain any number of variables.
TestReport.teardown.action.operation (operation)is equivalent toTestReport.teardown.action.operationElement `TestReport.teardown.action.operation` is mapped to FHIR R4B element `TestReport.teardown.action.operation` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/TestReport|3.0.2 to STU3: meta additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
TestReport.meta (meta)is equivalent toExtension (STU3: meta additional types)Element `TestReport.meta` is mapped to FHIR R4B element `TestReport.meta` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.meta` do not cover the following types: Meta. The mappings for `TestReport.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/TestReport|3.0.2 to STU3: text additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
TestReport.text (text)is equivalent toExtension (STU3: text additional types)Element `TestReport.text` is mapped to FHIR R4B element `TestReport.text` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.text` do not cover the following types: Narrative. The mappings for `TestReport.text` do not cover the following types based on type expansion: div, status. 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/TestReport|3.0.2 to STU3: identifier additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
TestReport.identifier (identifier)is equivalent toExtension (STU3: identifier additional types)Element `TestReport.identifier` is mapped to FHIR R4B element `TestReport.identifier` as `SourceIsBroaderThanTarget`. The mappings for `TestReport.identifier` do not cover the following types: Identifier. The mappings for `TestReport.identifier` do not cover the following types based on type expansion: assigner, period, system, type, use, value.