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

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

ConceptMap: R5CareTeamElementMapToR4

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

This ConceptMap represents cross-version mappings for elements from a FHIR R5 CareTeam to FHIR R4.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/CareTeam|5.0.0 to CareTeamversion: 4.0.1)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/CareTeam|5.0.0Codes from CareTeam
CareTeam.metameta​is equivalent toCareTeam.metaCareTeam.metaElement `CareTeam.meta` is mapped to FHIR R4 element `CareTeam.meta` as `Equivalent`.
CareTeam.implicitRulesimplicitRules​is equivalent toCareTeam.implicitRulesCareTeam.implicitRulesElement `CareTeam.implicitRules` is mapped to FHIR R4 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 its narrative along with other profiles, value sets, etc.
CareTeam.languagelanguage​is equivalent toCareTeam.languageCareTeam.languageElement `CareTeam.language` is mapped to FHIR R4 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).
CareTeam.texttext​is equivalent toCareTeam.textCareTeam.textElement `CareTeam.text` is mapped to FHIR R4 element `CareTeam.text` as `Equivalent`. Contained resources do not have a 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.
CareTeam.containedcontained​is equivalent toCareTeam.containedCareTeam.containedElement `CareTeam.contained` is mapped to FHIR R4 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.
CareTeam.identifieridentifier​is equivalent toCareTeam.identifierCareTeam.identifierElement `CareTeam.identifier` is mapped to FHIR R4 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.
CareTeam.statusstatus​is equivalent toCareTeam.statusCareTeam.statusElement `CareTeam.status` is mapped to FHIR R4 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.
CareTeam.categorycategory​is equivalent toCareTeam.categoryCareTeam.categoryElement `CareTeam.category` is mapped to FHIR R4 element `CareTeam.category` as `Equivalent`. There may be multiple axis of categorization and one team may serve multiple purposes.
CareTeam.namename​is equivalent toCareTeam.nameCareTeam.nameElement `CareTeam.name` is mapped to FHIR R4 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.).
CareTeam.subjectsubject​is equivalent toCareTeam.subjectCareTeam.subjectElement `CareTeam.subject` is mapped to FHIR R4 element `CareTeam.subject` as `Equivalent`. Use Group for care provision to all members of the group (e.g. group therapy). Use Patient for care provision to an individual patient.
CareTeam.periodperiod​is equivalent toCareTeam.periodCareTeam.periodElement `CareTeam.period` is mapped to FHIR R4 element `CareTeam.period` as `Equivalent`.
CareTeam.participantparticipant​maps to wider conceptCareTeam.participantCareTeam.participantElement `CareTeam.participant` is mapped to FHIR R4 element `CareTeam.participant` as `Equivalent`.
CareTeam.participant.rolerole​is equivalent toCareTeam.participant.roleCareTeam.participant.roleElement `CareTeam.participant.role` is mapped to FHIR R4 element `CareTeam.participant.role` as `SourceIsNarrowerThanTarget`. 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. If a participant has multiple roles within the team, then there should be multiple participants.
CareTeam.participant.membermember​is equivalent toCareTeam.participant.memberCareTeam.participant.memberElement `CareTeam.participant.member` is mapped to FHIR R4 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.
CareTeam.participant.onBehalfOfonBehalfOf​is equivalent toCareTeam.participant.onBehalfOfCareTeam.participant.onBehalfOfElement `CareTeam.participant.onBehalfOf` is mapped to FHIR R4 element `CareTeam.participant.onBehalfOf` as `Equivalent`.
CareTeam.reasonreason​is related toCareTeam.reasonCodeCareTeam.reasonCodeElement `CareTeam.reason` is mapped to FHIR R4 element `CareTeam.reasonCode` as `SourceIsBroaderThanTarget`. Element `CareTeam.reason` is mapped to FHIR R4 element `CareTeam.reasonReference` as `SourceIsBroaderThanTarget`.
​is related toCareTeam.reasonReferenceCareTeam.reasonReferenceElement `CareTeam.reason` is mapped to FHIR R4 element `CareTeam.reasonCode` as `SourceIsBroaderThanTarget`. Element `CareTeam.reason` is mapped to FHIR R4 element `CareTeam.reasonReference` as `SourceIsBroaderThanTarget`.
CareTeam.managingOrganizationmanagingOrganization​is equivalent toCareTeam.managingOrganizationCareTeam.managingOrganizationElement `CareTeam.managingOrganization` is mapped to FHIR R4 element `CareTeam.managingOrganization` as `Equivalent`.
CareTeam.telecomtelecom​is equivalent toCareTeam.telecomCareTeam.telecomElement `CareTeam.telecom` is mapped to FHIR R4 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.
CareTeam.notenote​is equivalent toCareTeam.noteCareTeam.noteElement `CareTeam.note` is mapped to FHIR R4 element `CareTeam.note` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/CareTeam|5.0.0 to R5: When the member is generally available within this care team (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
CareTeam.participant.coverage[x] (coverage[x])​maps to wider conceptExtension (R5: When the member is generally available within this care team (new))Element `CareTeam.participant.coverage[x]` has a context of CareTeam.participant based on following the parent source element upwards and mapping to `CareTeam`. Element `CareTeam.participant.coverage[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This is populated while creating / managing the CareTeam to ensure there is coverage when servicing CarePlan activities from the Schedule.