Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5
0.1.0 - STU
Extensions for Using Data Elements from FHIR R4 in FHIR R5 - Downloaded Version null See the Directory of published versions
| Page standards status: Trial-use | Maturity Level: 0 |
<ConceptMap xmlns="http://hl7.org/fhir">
<id value="R4-CareTeam-element-map-to-R5"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: ConceptMap R4-CareTeam-element-map-to-R5</b></p><a name="R4-CareTeam-element-map-to-R5"> </a><a name="hcR4-CareTeam-element-map-to-R5"> </a><p>Mapping from http://hl7.org/fhir/4.0 to http://hl7.org/fhir/5.0</p><br/><p><b>Group 1 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1</code> to <a href="http://hl7.org/fhir/R5/careteam.html">CareTeamversion: 5.0.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>CareTeam.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>CareTeam.meta</td><td>Element `CareTeam.meta` is mapped to FHIR R5 element `CareTeam.meta` as `Equivalent`.</td></tr><tr><td>CareTeam.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>CareTeam.implicitRules</td><td>Element `CareTeam.implicitRules` is mapped to FHIR R5 element `CareTeam.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.</td></tr><tr><td>CareTeam.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>CareTeam.language</td><td>Element `CareTeam.language` is mapped to FHIR R5 element `CareTeam.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).</td></tr><tr><td>CareTeam.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>CareTeam.text</td><td>Element `CareTeam.text` is mapped to FHIR R5 element `CareTeam.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.</td></tr><tr><td>CareTeam.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>CareTeam.contained</td><td>Element `CareTeam.contained` is mapped to FHIR R5 element `CareTeam.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.</td></tr><tr><td>CareTeam.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>CareTeam.identifier</td><td>Element `CareTeam.identifier` is mapped to FHIR R5 element `CareTeam.identifier` as `Equivalent`.
This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number.</td></tr><tr><td>CareTeam.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>CareTeam.status</td><td>Element `CareTeam.status` is mapped to FHIR R5 element `CareTeam.status` as `Equivalent`.
This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid.</td></tr><tr><td>CareTeam.category (category)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.category</td><td>Element `CareTeam.category` is mapped to FHIR R5 element `CareTeam.category` as `Equivalent`.
There may be multiple axis of categorization and one team may serve multiple purposes.</td></tr><tr><td>CareTeam.name (name)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.name</td><td>Element `CareTeam.name` is mapped to FHIR R5 element `CareTeam.name` as `Equivalent`.
The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.).</td></tr><tr><td>CareTeam.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>CareTeam.subject</td><td>Element `CareTeam.subject` is mapped to FHIR R5 element `CareTeam.subject` as `Equivalent`.</td></tr><tr><td>CareTeam.period (period)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.period</td><td>Element `CareTeam.period` is mapped to FHIR R5 element `CareTeam.period` as `Equivalent`.</td></tr><tr><td>CareTeam.participant (participant)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#source-is-broader-than-target" title="source-is-broader-than-target">is broader than</a></td><td>CareTeam.participant</td><td>Element `CareTeam.participant` is mapped to FHIR R5 element `CareTeam.participant` as `Equivalent`.</td></tr><tr><td>CareTeam.participant.role (role)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.participant.role</td><td>Element `CareTeam.participant.role` is mapped to FHIR R5 element `CareTeam.participant.role` as `SourceIsBroaderThanTarget`.
Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly.</td></tr><tr><td>CareTeam.participant.member (member)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.participant.member</td><td>Element `CareTeam.participant.member` is mapped to FHIR R5 element `CareTeam.participant.member` as `Equivalent`.
Patient only needs to be listed if they have a role other than "subject of care".
Member is optional because some participants may be known only by their role, particularly in draft plans.</td></tr><tr><td>CareTeam.participant.onBehalfOf (onBehalfOf)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.participant.onBehalfOf</td><td>Element `CareTeam.participant.onBehalfOf` is mapped to FHIR R5 element `CareTeam.participant.onBehalfOf` as `Equivalent`.</td></tr><tr><td>CareTeam.managingOrganization (managingOrganization)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.managingOrganization</td><td>Element `CareTeam.managingOrganization` is mapped to FHIR R5 element `CareTeam.managingOrganization` as `Equivalent`.</td></tr><tr><td>CareTeam.telecom (telecom)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>CareTeam.telecom</td><td>Element `CareTeam.telecom` is mapped to FHIR R5 element `CareTeam.telecom` as `Equivalent`.
The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members.</td></tr><tr><td>CareTeam.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>CareTeam.note</td><td>Element `CareTeam.note` is mapped to FHIR R5 element `CareTeam.note` as `Equivalent`.</td></tr></table><hr/><p><b>Group 2 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1</code> to <a href="StructureDefinition-ext-R4-CareTeam.encounter.html">R4: Encounter created as part of (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>CareTeam.encounter (encounter)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: Encounter created as part of (new))</td><td>Element `CareTeam.encounter` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.encounter` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter.</td></tr></table><hr/><p><b>Group 3 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1</code> to <a href="StructureDefinition-ext-R4-CareTeam.par.period.html">R4: Time period of participant (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>CareTeam.participant.period (period)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: Time period of participant (new))</td><td>Element `CareTeam.participant.period` has a context of CareTeam.participant based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.participant.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 4 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1</code> to <a href="StructureDefinition-ext-R4-CareTeam.reasonCode.html">R4: Why the care team exists (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>CareTeam.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>Extension (R4: Why the care team exists (new))</td><td>Element `CareTeam.reasonCode` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.reasonCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table><hr/><p><b>Group 5 </b>Mapping from <code>http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1</code> to <a href="StructureDefinition-ext-R4-CareTeam.reasonReference.html">R4: Why the care team exists (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>CareTeam.reasonReference (reasonReference)</td><td><a href="http://hl7.org/fhir/R5/codesystem-concept-map-relationship.html#equivalent" title="equivalent">is equivalent to</a></td><td>Extension (R4: Why the care team exists (new))</td><td>Element `CareTeam.reasonReference` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.reasonReference` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).</td></tr></table></div>
</text>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
<valueCode value="fhir"/>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
<valueInteger value="0">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"/>
</extension>
</valueInteger>
</extension>
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
<valueCode value="trial-use">
<extension
url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
<valueCanonical
value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r4.r5"/>
</extension>
</valueCode>
</extension>
<url
value="http://hl7.org/fhir/uv/xver/ConceptMap/R4-CareTeam-element-map-to-R5"/>
<version value="0.1.0"/>
<name value="R4CareTeamElementMapToR5"/>
<title
value="Cross-version mapping for FHIR R4 CareTeam to FHIR R5 CareTeam"/>
<status value="active"/>
<experimental value="false"/>
<date value="2026-03-17T16:04:34.4832413-05:00"/>
<contact>
<name value="FHIR Infrastructure"/>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/fiwg"/>
</telecom>
</contact>
<description
value="This ConceptMap represents cross-version mappings for elements from a FHIR R4 CareTeam to FHIR R5."/>
<jurisdiction>
<coding>
<system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
<code value="001"/>
<display value="World"/>
</coding>
</jurisdiction>
<sourceScopeCanonical value="http://hl7.org/fhir/4.0"/>
<targetScopeUri value="http://hl7.org/fhir/5.0"/>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1"/>
<target value="http://hl7.org/fhir/StructureDefinition/CareTeam|5.0.0"/>
<element>
<code value="CareTeam.meta"/>
<display value="meta"/>
<target>
<code value="CareTeam.meta"/>
<display value="CareTeam.meta"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.meta` is mapped to FHIR R5 element `CareTeam.meta` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.implicitRules"/>
<display value="implicitRules"/>
<target>
<code value="CareTeam.implicitRules"/>
<display value="CareTeam.implicitRules"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.implicitRules` is mapped to FHIR R5 element `CareTeam.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."/>
</target>
</element>
<element>
<code value="CareTeam.language"/>
<display value="language"/>
<target>
<code value="CareTeam.language"/>
<display value="CareTeam.language"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.language` is mapped to FHIR R5 element `CareTeam.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)."/>
</target>
</element>
<element>
<code value="CareTeam.text"/>
<display value="text"/>
<target>
<code value="CareTeam.text"/>
<display value="CareTeam.text"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.text` is mapped to FHIR R5 element `CareTeam.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."/>
</target>
</element>
<element>
<code value="CareTeam.contained"/>
<display value="contained"/>
<target>
<code value="CareTeam.contained"/>
<display value="CareTeam.contained"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.contained` is mapped to FHIR R5 element `CareTeam.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."/>
</target>
</element>
<element>
<code value="CareTeam.identifier"/>
<display value="identifier"/>
<target>
<code value="CareTeam.identifier"/>
<display value="CareTeam.identifier"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.identifier` is mapped to FHIR R5 element `CareTeam.identifier` as `Equivalent`.
This is a business identifier, not a resource identifier (see [discussion](https://hl7.org/fhir/resource.htm#identifiers)). It is best practice for the identifier to only appear on a single resource instance, however business practices may occasionally dictate that multiple resource instances with the same identifier can exist - possibly even with different resource types. For example, multiple Patient and a Person resource instance might share the same social insurance number."/>
</target>
</element>
<element>
<code value="CareTeam.status"/>
<display value="status"/>
<target>
<code value="CareTeam.status"/>
<display value="CareTeam.status"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.status` is mapped to FHIR R5 element `CareTeam.status` as `Equivalent`.
This element is labeled as a modifier because the status contains the code entered-in-error that marks the care team as not currently valid."/>
</target>
</element>
<element>
<code value="CareTeam.category"/>
<display value="category"/>
<target>
<code value="CareTeam.category"/>
<display value="CareTeam.category"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.category` is mapped to FHIR R5 element `CareTeam.category` as `Equivalent`.
There may be multiple axis of categorization and one team may serve multiple purposes."/>
</target>
</element>
<element>
<code value="CareTeam.name"/>
<display value="name"/>
<target>
<code value="CareTeam.name"/>
<display value="CareTeam.name"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.name` is mapped to FHIR R5 element `CareTeam.name` as `Equivalent`.
The meaning/purpose of the team is conveyed in CareTeam.category. This element may also convey semantics of the team (e.g. "Red trauma team"), but its primary purpose is to distinguish between identical teams in a human-friendly way. ("Team 18735" isn't as friendly.)."/>
</target>
</element>
<element>
<code value="CareTeam.subject"/>
<display value="subject"/>
<target>
<code value="CareTeam.subject"/>
<display value="CareTeam.subject"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.subject` is mapped to FHIR R5 element `CareTeam.subject` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.period"/>
<display value="period"/>
<target>
<code value="CareTeam.period"/>
<display value="CareTeam.period"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.period` is mapped to FHIR R5 element `CareTeam.period` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.participant"/>
<display value="participant"/>
<target>
<code value="CareTeam.participant"/>
<display value="CareTeam.participant"/>
<relationship value="source-is-broader-than-target"/>
<comment
value="Element `CareTeam.participant` is mapped to FHIR R5 element `CareTeam.participant` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.participant.role"/>
<display value="role"/>
<target>
<code value="CareTeam.participant.role"/>
<display value="CareTeam.participant.role"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.participant.role` is mapped to FHIR R5 element `CareTeam.participant.role` as `SourceIsBroaderThanTarget`.
Roles may sometimes be inferred by type of Practitioner. These are relationships that hold only within the context of the care team. General relationships should be handled as properties of the Patient resource directly."/>
</target>
</element>
<element>
<code value="CareTeam.participant.member"/>
<display value="member"/>
<target>
<code value="CareTeam.participant.member"/>
<display value="CareTeam.participant.member"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.participant.member` is mapped to FHIR R5 element `CareTeam.participant.member` as `Equivalent`.
Patient only needs to be listed if they have a role other than "subject of care".
Member is optional because some participants may be known only by their role, particularly in draft plans."/>
</target>
</element>
<element>
<code value="CareTeam.participant.onBehalfOf"/>
<display value="onBehalfOf"/>
<target>
<code value="CareTeam.participant.onBehalfOf"/>
<display value="CareTeam.participant.onBehalfOf"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.participant.onBehalfOf` is mapped to FHIR R5 element `CareTeam.participant.onBehalfOf` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.managingOrganization"/>
<display value="managingOrganization"/>
<target>
<code value="CareTeam.managingOrganization"/>
<display value="CareTeam.managingOrganization"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.managingOrganization` is mapped to FHIR R5 element `CareTeam.managingOrganization` as `Equivalent`."/>
</target>
</element>
<element>
<code value="CareTeam.telecom"/>
<display value="telecom"/>
<target>
<code value="CareTeam.telecom"/>
<display value="CareTeam.telecom"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.telecom` is mapped to FHIR R5 element `CareTeam.telecom` as `Equivalent`.
The ContactPoint.use code of home is not appropriate to use. These contacts are not the contact details of individual care team members."/>
</target>
</element>
<element>
<code value="CareTeam.note"/>
<display value="note"/>
<target>
<code value="CareTeam.note"/>
<display value="CareTeam.note"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.note` is mapped to FHIR R5 element `CareTeam.note` as `Equivalent`."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-CareTeam.encounter|0.1.0"/>
<element>
<code value="CareTeam.encounter"/>
<display value="encounter"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.encounter` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.encounter` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-CareTeam.participant.period|0.1.0"/>
<element>
<code value="CareTeam.participant.period"/>
<display value="period"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.participant.period` has a context of CareTeam.participant based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.participant.period` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-CareTeam.reasonCode|0.1.0"/>
<element>
<code value="CareTeam.reasonCode"/>
<display value="reasonCode"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.reasonCode` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.reasonCode` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
<group>
<source value="http://hl7.org/fhir/StructureDefinition/CareTeam|4.0.1"/>
<target
value="http://hl7.org/fhir/4.0/StructureDefinition/extension-CareTeam.reasonReference|0.1.0"/>
<element>
<code value="CareTeam.reasonReference"/>
<display value="reasonReference"/>
<target>
<code value="Extension"/>
<relationship value="equivalent"/>
<comment
value="Element `CareTeam.reasonReference` has a context of CareTeam based on following the parent source element upwards and mapping to `CareTeam`.
Element `CareTeam.reasonReference` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element)."/>
</target>
</element>
</group>
</ConceptMap>
IG © 2025+ FHIR Infrastructure. Package hl7.fhir.uv.xver-r4.r5#0.1.0 based on FHIR 5.0.0. Generated 2026-03-20
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change