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

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

Lookup for Profile_R5_TestReport_R4B

Lookup for FHIR R5 TestReport for use in FHIR R4B

The FHIR R5 resource is represented in FHIR R4B via the TestReport resource.

Note that there is a profile defined to simplify use of this cross-version resource representation:Profile: TestReport

A computable version of the following element information is available in: R5TestReportElementMapToR4B

Source Element (FHIR R5) Target(s) Comments
TestReport    
TestReport.meta TestReport.meta Element TestReport.meta is mapped to FHIR R4B element TestReport.meta as Equivalent.
TestReport.implicitRules TestReport.implicitRules Element TestReport.implicitRules is mapped to FHIR R4B element TestReport.implicitRules as Equivalent.
TestReport.language TestReport.language Element TestReport.language is mapped to FHIR R4B element TestReport.language as Equivalent.
TestReport.text TestReport.text Element TestReport.text is mapped to FHIR R4B element TestReport.text as Equivalent.
TestReport.contained TestReport.contained Element TestReport.contained is mapped to FHIR R4B element TestReport.contained as Equivalent.
TestReport.identifier TestReport.identifier Element TestReport.identifier is mapped to FHIR R4B element TestReport.identifier as Equivalent.
TestReport.name TestReport.name Element TestReport.name is mapped to FHIR R4B element TestReport.name as Equivalent.
TestReport.status TestReport.status Element TestReport.status is mapped to FHIR R4B element TestReport.status as Equivalent.
TestReport.testScript TestReport.testScript
Extension: ExtensionTestReport_TestScript		 Element TestReport.testScript is mapped to FHIR R4B element TestReport.testScript as SourceIsBroaderThanTarget.
The mappings for TestReport.testScript do not cover the following types: canonical.
The mappings for TestReport.testScript do not cover the following types based on type expansion: value.
TestReport.result TestReport.result Element TestReport.result is mapped to FHIR R4B element TestReport.result as Equivalent.
TestReport.score TestReport.score Element TestReport.score is mapped to FHIR R4B element TestReport.score as Equivalent.
TestReport.tester TestReport.tester Element TestReport.tester is mapped to FHIR R4B element TestReport.tester as Equivalent.
TestReport.issued TestReport.issued Element TestReport.issued is mapped to FHIR R4B element TestReport.issued as Equivalent.
TestReport.participant TestReport.participant Element TestReport.participant is mapped to FHIR R4B element TestReport.participant as Equivalent.
TestReport.participant.type TestReport.participant.type Element TestReport.participant.type is mapped to FHIR R4B element TestReport.participant.type as Equivalent.
TestReport.participant.uri TestReport.participant.uri Element TestReport.participant.uri is mapped to FHIR R4B element TestReport.participant.uri as Equivalent.
TestReport.participant.display TestReport.participant.display Element TestReport.participant.display is mapped to FHIR R4B element TestReport.participant.display as Equivalent.
TestReport.setup TestReport.setup Element TestReport.setup is mapped to FHIR R4B element TestReport.setup as Equivalent.
TestReport.setup.action TestReport.setup.action Element TestReport.setup.action is mapped to FHIR R4B element TestReport.setup.action as Equivalent.
TestReport.setup.action.operation TestReport.setup.action.operation Element TestReport.setup.action.operation is mapped to FHIR R4B element TestReport.setup.action.operation as Equivalent.
TestReport.setup.action.operation.result TestReport.setup.action.operation.result Element TestReport.setup.action.operation.result is mapped to FHIR R4B element TestReport.setup.action.operation.result as Equivalent.
TestReport.setup.action.operation.message TestReport.setup.action.operation.message Element TestReport.setup.action.operation.message is mapped to FHIR R4B element TestReport.setup.action.operation.message as Equivalent.
TestReport.setup.action.operation.detail TestReport.setup.action.operation.detail Element TestReport.setup.action.operation.detail is mapped to FHIR R4B element TestReport.setup.action.operation.detail as Equivalent.
TestReport.setup.action.assert TestReport.setup.action.assert Element TestReport.setup.action.assert is mapped to FHIR R4B element TestReport.setup.action.assert as Equivalent.
TestReport.setup.action.assert.result TestReport.setup.action.assert.result Element TestReport.setup.action.assert.result is mapped to FHIR R4B element TestReport.setup.action.assert.result as Equivalent.
TestReport.setup.action.assert.message TestReport.setup.action.assert.message Element TestReport.setup.action.assert.message is mapped to FHIR R4B element TestReport.setup.action.assert.message as Equivalent.
TestReport.setup.action.assert.detail TestReport.setup.action.assert.detail Element TestReport.setup.action.assert.detail is mapped to FHIR R4B element TestReport.setup.action.assert.detail as Equivalent.
TestReport.setup.action.assert.requirement Extension: ExtensionTestReport_Setup_Action_Assert_Requirement Element TestReport.setup.action.assert.requirement has a context of TestReport.setup.action.assert based on following the parent source element upwards and mapping to TestReport.
Element TestReport.setup.action.assert.requirement has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
TestReport.setup.action.assert.requirement.link[x] Extension: ExtensionTestReport_Setup_Action_Assert_Requirement Slice:link Element TestReport.setup.action.assert.requirement.link[x] is part of an existing definition because parent element TestReport.setup.action.assert.requirement requires a cross-version extension.
Element TestReport.setup.action.assert.requirement.link[x] has a context of TestReport.setup.action.assert based on following the parent source element upwards and mapping to TestReport.
Element TestReport.setup.action.assert.requirement.link[x] has no mapping targets in FHIR R4B. Typically, this is because the element has been added (is a new element).
TestReport.test TestReport.test Element TestReport.test is mapped to FHIR R4B element TestReport.test as Equivalent.
TestReport.test.name TestReport.test.name Element TestReport.test.name is mapped to FHIR R4B element TestReport.test.name as Equivalent.
TestReport.test.description TestReport.test.description Element TestReport.test.description is mapped to FHIR R4B element TestReport.test.description as Equivalent.
TestReport.test.action TestReport.test.action Element TestReport.test.action is mapped to FHIR R4B element TestReport.test.action as Equivalent.
TestReport.test.action.operation TestReport.test.action.operation Element TestReport.test.action.operation is mapped to FHIR R4B element TestReport.test.action.operation as Equivalent.
TestReport.test.action.assert TestReport.test.action.assert Element TestReport.test.action.assert is mapped to FHIR R4B element TestReport.test.action.assert as Equivalent.
TestReport.teardown TestReport.teardown Element TestReport.teardown is mapped to FHIR R4B element TestReport.teardown as Equivalent.
TestReport.teardown.action TestReport.teardown.action Element TestReport.teardown.action is mapped to FHIR R4B element TestReport.teardown.action as Equivalent.
TestReport.teardown.action.operation TestReport.teardown.action.operation Element TestReport.teardown.action.operation is mapped to FHIR R4B element TestReport.teardown.action.operation as Equivalent.