Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR STU3
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR STU3 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
{
"resourceType" : "ConceptMap",
"id" : "R4-DeviceUseStatement-element-map-to-R3",
"text" : {
"status" : "generated",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ConceptMap R4-DeviceUseStatement-element-map-to-R3</b></p><a name=\"R4-DeviceUseStatement-element-map-to-R3\"> </a><a name=\"hcR4-DeviceUseStatement-element-map-to-R3\"> </a><p>Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/3.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1</code> to <code>http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|3.0.2</code></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>DeviceUseStatement.meta (meta)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.meta</td><td>Element `DeviceUseStatement.meta` is mapped to FHIR STU3 element `DeviceUseStatement.meta` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.implicitRules (implicitRules)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.implicitRules</td><td>Element `DeviceUseStatement.implicitRules` is mapped to FHIR STU3 element `DeviceUseStatement.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 it's narrative along with other profiles, value sets, etc.</td></tr><tr><td>DeviceUseStatement.language (language)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.language</td><td>Element `DeviceUseStatement.language` is mapped to FHIR STU3 element `DeviceUseStatement.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).</td></tr><tr><td>DeviceUseStatement.text (text)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.text</td><td>Element `DeviceUseStatement.text` is mapped to FHIR STU3 element `DeviceUseStatement.text` as `Equivalent`.\nContained 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.</td></tr><tr><td>DeviceUseStatement.contained (contained)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.contained</td><td>Element `DeviceUseStatement.contained` is mapped to FHIR STU3 element `DeviceUseStatement.contained` as `Equivalent`.\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.</td></tr><tr><td>DeviceUseStatement.identifier (identifier)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.identifier</td><td>Element `DeviceUseStatement.identifier` is mapped to FHIR STU3 element `DeviceUseStatement.identifier` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.status (status)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.status</td><td>Element `DeviceUseStatement.status` is mapped to FHIR STU3 element `DeviceUseStatement.status` as `Equivalent`.\nDeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).\r\rThis element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid.</td></tr><tr><td>DeviceUseStatement.subject (subject)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.subject</td><td>Element `DeviceUseStatement.subject` is mapped to FHIR STU3 element `DeviceUseStatement.subject` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.timing[x] (timing[x])</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.timing[x]</td><td>Element `DeviceUseStatement.timing[x]` is mapped to FHIR STU3 element `DeviceUseStatement.timing[x]` as `Equivalent`.\nThe target context `DeviceUseStatement.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceUseStatement`.</td></tr><tr><td>DeviceUseStatement.recordedOn (recordedOn)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.recordedOn</td><td>Element `DeviceUseStatement.recordedOn` is mapped to FHIR STU3 element `DeviceUseStatement.recordedOn` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.source (source)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>DeviceUseStatement.source</td><td>Element `DeviceUseStatement.source` is mapped to FHIR STU3 element `DeviceUseStatement.source` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `DeviceUseStatement.source` with unmapped reference targets: PractitionerRole.</td></tr><tr><td>DeviceUseStatement.device (device)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.device</td><td>Element `DeviceUseStatement.device` is mapped to FHIR STU3 element `DeviceUseStatement.device` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.reasonCode (reasonCode)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.indication</td><td>Element `DeviceUseStatement.reasonCode` is mapped to FHIR STU3 element `DeviceUseStatement.indication` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.bodySite (bodySite)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.bodySite</td><td>Element `DeviceUseStatement.bodySite` is mapped to FHIR STU3 element `DeviceUseStatement.bodySite` as `Equivalent`.</td></tr><tr><td>DeviceUseStatement.note (note)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent\" title=\"equivalent\">is equivalent to</a></td><td>DeviceUseStatement.note</td><td>Element `DeviceUseStatement.note` is mapped to FHIR STU3 element `DeviceUseStatement.note` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1</code> to <a href=\"StructureDefinition-ext-R4-DeviceUseStatement.basedOn.html\">R4: Fulfills plan, proposal or order (new)version: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>DeviceUseStatement.basedOn (basedOn)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Extension (R4: Fulfills plan, proposal or order (new))</td><td>Element `DeviceUseStatement.basedOn` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.basedOn` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1</code> to <a href=\"StructureDefinition-ext-R4-DeviceUseStatement.derivedFrom.html\">R4: Supporting information (new)version: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>DeviceUseStatement.derivedFrom (derivedFrom)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Extension (R4: Supporting information (new))</td><td>Element `DeviceUseStatement.derivedFrom` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.derivedFrom` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from.</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/DeviceUseStatement|4.0.1</code> to <a href=\"StructureDefinition-ext-R4-DeviceUseStatement.reasonReference.html\">R4: Why was DeviceUseStatement performed? (new)version: 0.1.0)</a></p><table class=\"grid\"><tr><td><b>Source Code</b></td><td><b>Relationship</b></td><td><b>Target Code</b></td><td><b>Comment</b></td></tr><tr><td>DeviceUseStatement.reasonReference (reasonReference)</td><td><a href=\"http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#wider\" title=\"wider\">maps to wider concept</a></td><td>Extension (R4: Why was DeviceUseStatement performed? (new))</td><td>Element `DeviceUseStatement.reasonReference` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.reasonReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).</td></tr></table></div>"
},
"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-r4.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-r4.r3"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/xver/ConceptMap/R4-DeviceUseStatement-element-map-to-R3",
"version" : "0.1.0",
"name" : "R4DeviceUseStatementElementMapToR3",
"title" : "Cross-version mapping for FHIR R4 DeviceUseStatement to FHIR STU3 DeviceUseStatement",
"status" : "active",
"experimental" : false,
"date" : "2026-03-17T16:03:31.1339962-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 R4 DeviceUseStatement to FHIR STU3.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"sourceUri" : "http://hl7.org/fhir/4.0",
"targetUri" : "http://hl7.org/fhir/3.0",
"group" : [
{
"source" : "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
"sourceVersion" : "4.0.1",
"target" : "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
"targetVersion" : "3.0.2",
"element" : [
{
"code" : "DeviceUseStatement.meta",
"display" : "meta",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.meta",
"display" : "DeviceUseStatement.meta",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.meta` is mapped to FHIR STU3 element `DeviceUseStatement.meta` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.implicitRules",
"display" : "implicitRules",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.implicitRules",
"display" : "DeviceUseStatement.implicitRules",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.implicitRules` is mapped to FHIR STU3 element `DeviceUseStatement.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 it's narrative along with other profiles, value sets, etc."
}
]
},
{
"code" : "DeviceUseStatement.language",
"display" : "language",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.language",
"display" : "DeviceUseStatement.language",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.language` is mapped to FHIR STU3 element `DeviceUseStatement.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" : "DeviceUseStatement.text",
"display" : "text",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.text",
"display" : "DeviceUseStatement.text",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.text` is mapped to FHIR STU3 element `DeviceUseStatement.text` as `Equivalent`.\nContained 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."
}
]
},
{
"code" : "DeviceUseStatement.contained",
"display" : "contained",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.contained",
"display" : "DeviceUseStatement.contained",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.contained` is mapped to FHIR STU3 element `DeviceUseStatement.contained` as `Equivalent`.\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" : "DeviceUseStatement.identifier",
"display" : "identifier",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.identifier",
"display" : "DeviceUseStatement.identifier",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.identifier` is mapped to FHIR STU3 element `DeviceUseStatement.identifier` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.status",
"display" : "status",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.status",
"display" : "DeviceUseStatement.status",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.status` is mapped to FHIR STU3 element `DeviceUseStatement.status` as `Equivalent`.\nDeviceUseStatment is a statement at a point in time. The status is only representative at the point when it was asserted. The value set for contains codes that assert the status of the use by the patient (for example, stopped or on hold) as well as codes that assert the status of the resource itself (for example, entered in error).\r\rThis element is labeled as a modifier because the status contains the codes that mark the statement as not currently valid."
}
]
},
{
"code" : "DeviceUseStatement.subject",
"display" : "subject",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.subject",
"display" : "DeviceUseStatement.subject",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.subject` is mapped to FHIR STU3 element `DeviceUseStatement.subject` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.timing[x]",
"display" : "timing[x]",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.timing[x]",
"display" : "DeviceUseStatement.timing[x]",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.timing[x]` is mapped to FHIR STU3 element `DeviceUseStatement.timing[x]` as `Equivalent`.\nThe target context `DeviceUseStatement.timing[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `DeviceUseStatement`."
}
]
},
{
"code" : "DeviceUseStatement.recordedOn",
"display" : "recordedOn",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.recordedOn",
"display" : "DeviceUseStatement.recordedOn",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.recordedOn` is mapped to FHIR STU3 element `DeviceUseStatement.recordedOn` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.source",
"display" : "source",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "wider"
}
],
"code" : "DeviceUseStatement.source",
"display" : "DeviceUseStatement.source",
"equivalence" : "wider",
"comment" : "Element `DeviceUseStatement.source` is mapped to FHIR STU3 element `DeviceUseStatement.source` as `SourceIsBroaderThanTarget`.\nThe standard extension `alternate-reference` has been mapped as the representation of FHIR R4 element `DeviceUseStatement.source` with unmapped reference targets: PractitionerRole."
}
]
},
{
"code" : "DeviceUseStatement.device",
"display" : "device",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.device",
"display" : "DeviceUseStatement.device",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.device` is mapped to FHIR STU3 element `DeviceUseStatement.device` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.reasonCode",
"display" : "reasonCode",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.indication",
"display" : "DeviceUseStatement.indication",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.reasonCode` is mapped to FHIR STU3 element `DeviceUseStatement.indication` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.bodySite",
"display" : "bodySite",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.bodySite",
"display" : "DeviceUseStatement.bodySite",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.bodySite` is mapped to FHIR STU3 element `DeviceUseStatement.bodySite` as `Equivalent`."
}
]
},
{
"code" : "DeviceUseStatement.note",
"display" : "note",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "equivalent"
}
],
"code" : "DeviceUseStatement.note",
"display" : "DeviceUseStatement.note",
"equivalence" : "equivalent",
"comment" : "Element `DeviceUseStatement.note` is mapped to FHIR STU3 element `DeviceUseStatement.note` as `Equivalent`."
}
]
}
]
},
{
"source" : "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
"sourceVersion" : "4.0.1",
"target" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-DeviceUseStatement.basedOn",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "DeviceUseStatement.basedOn",
"display" : "basedOn",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "wider"
}
],
"code" : "Extension",
"equivalence" : "wider",
"comment" : "Element `DeviceUseStatement.basedOn` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.basedOn` 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/DeviceUseStatement",
"sourceVersion" : "4.0.1",
"target" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-DeviceUseStatement.derivedFrom",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "DeviceUseStatement.derivedFrom",
"display" : "derivedFrom",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "wider"
}
],
"code" : "Extension",
"equivalence" : "wider",
"comment" : "Element `DeviceUseStatement.derivedFrom` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.derivedFrom` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).\nThe most common use cases for deriving a DeviceUseStatement comes from creating it from a request or from an observation or a claim. it should be noted that the amount of information that is available varies from the type resource that you derive the DeviceUseStatement from."
}
]
}
]
},
{
"source" : "http://hl7.org/fhir/StructureDefinition/DeviceUseStatement",
"sourceVersion" : "4.0.1",
"target" : "http://hl7.org/fhir/4.0/StructureDefinition/extension-DeviceUseStatement.reasonReference",
"targetVersion" : "0.1.0",
"element" : [
{
"code" : "DeviceUseStatement.reasonReference",
"display" : "reasonReference",
"target" : [
{
"modifierExtension" : [
{
"url" : "http://hl7.org/fhir/1.0/StructureDefinition/extension-ConceptMap.element.target.equivalence",
"valueCode" : "wider"
}
],
"code" : "Extension",
"equivalence" : "wider",
"comment" : "Element `DeviceUseStatement.reasonReference` has a context of DeviceUseStatement based on following the parent source element upwards and mapping to `DeviceUseStatement`.\nElement `DeviceUseStatement.reasonReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element)."
}
]
}
]
}
]
}
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r3#0.1.0 based on FHIR 3.0.2. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change