R3-ServiceDefinition-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R3-ServiceDefinition-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R3-ServiceDefinition-element-map-to-R4 Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ServiceDefinition|3.0.2 to Basicversion: 4.0.1) Source Code Relationship Target Code Comment ServiceDefinition.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ServiceDefinition.meta` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). ServiceDefinition.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ServiceDefinition.implicitRules` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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. ServiceDefinition.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ServiceDefinition.language` is not mapped to FHIR R4, since FHIR STU3 `ServiceDe…
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-wg
    l: structuredefinition-wg
  value: Code
    v: fhir
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm
    l: structuredefinition-fmm
  value: Integer
    v: 0
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4
        l: hl7.fhir.uv.xver-r3.r4
extension:
  url:
    v: http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status
    l: structuredefinition-standards-status
  value: Code
    v: trial-use
    extension:
      url:
        v: http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom
        l: structuredefinition-conformance-derivedFrom
      value: Canonical
        v: http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4
        l: hl7.fhir.uv.xver-r3.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R3-ServiceDefinition-element-map-to-R4
  l: R3-ServiceDefinition-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R3ServiceDefinitionElementMapToR4
title:
  v: Cross-version mapping for FHIR STU3 ServiceDefinition to FHIR R4 Basic
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:03:24.1702335-05:00
contact:
  name:
    v: FHIR Infrastructure
  telecom:
    system:
      v: url
    value:
      v: http://www.hl7.org/Special/committees/fiwg
description:
  v: This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ServiceDefinition to FHIR R4.
jurisdiction:
  coding:
    system:
      v: http://unstats.un.org/unsd/methods/m49/m49.htm
      l: m49.htm
    code:
      v: 001
    display:
      v: World
source: Canonical
  v: http://hl7.org/fhir/3.0
  l: http://hl7.org/fhir/3.0
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
    l: ServiceDefinition
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/StructureDefinition/Basic
    l: Basic
  target version:
    v: 4.0.1
  element:
    code:
      v: ServiceDefinition.meta
    display:
      v: meta
    target:
      code:
        v: Basic.meta
      display:
        v: Basic.meta
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `ServiceDefinition.meta` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
  element:
    code:
      v: ServiceDefinition.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: Basic.implicitRules
      display:
        v: Basic.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `ServiceDefinition.implicitRules` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
  element:
    code:
      v: ServiceDefinition.language
    display:
      v: language
    target:
      code:
        v: Basic.language
      display:
        v: Basic.language
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `ServiceDefinition.language` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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).
  element:
    code:
      v: ServiceDefinition.text
    display:
      v: text
    target:
      code:
        v: Basic.text
      display:
        v: Basic.text
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `ServiceDefinition.text` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
  element:
    code:
      v: ServiceDefinition.contained
    display:
      v: contained
    target:
      code:
        v: Basic.contained
      display:
        v: Basic.contained
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `ServiceDefinition.contained` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). 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.
  element:
    code:
      v: ServiceDefinition.identifier
    display:
      v: identifier
    target:
      code:
        v: Basic.identifier
      display:
        v: Basic.identifier
      equivalence:
        v: equivalent
      comment:
        v: Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `ServiceDefinition.identifier` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Typically, this is used for identifiers that can go in an HL7 V3 II (instance identifier) data type, e.g., to identify this service definition outside of FHIR, where it is not possible to use the logical URI.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
    l: ServiceDefinition
  source version:
    v: 3.0.2
  target:
    v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.url
    l: extension-ServiceDefinition.url
  target version:
    v: 0.1.0
  element:
    code:
      v: ServiceDefinition.url
    display:
      v: url
    target:
      code:
        v: Extension
      equivalence:
        v: wider
      comment:
        v: Element `ServiceDefinition.url` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid:, but real http: addresses are preferred. Multiple instances may share the same url if they have a distinct version.
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
    l: ServiceDefinition

v: 3.0.2

v: 0.1.0

code:
  v: ServiceDefinition.version
display:
  v: version
target:
  code:
    v: Extension
  equivalence:
    v: wider
  comment:
    v: Element `ServiceDefinition.version` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.version` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). There may be different service definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a refrence to a particular business version of the service definition with the format [url]|[version].

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.name
  l: extension-ServiceDefinition.name
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.name
  display:
    v: name
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.name` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.name` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The name is not expected to be globally unique. The name should be a simple alpha-numeric type name to ensure that it is computable friendly.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.title
  l: extension-ServiceDefinition.title
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.title
  display:
    v: title
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.title` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.status
  l: extension-ServiceDefinition.status
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.status
  display:
    v: status
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.status` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definitions that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired service definition without due consideration.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.experimental
  l: extension-ServiceDefinition.experimental
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.experimental
  display:
    v: experimental
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.experimental` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.experimental` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of service definition that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental service definition in production.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.date
  l: extension-ServiceDefinition.date
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.date
  display:
    v: date
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.date` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.date` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the service definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.publisher
  l: extension-ServiceDefinition.publisher
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.publisher
  display:
    v: publisher
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.publisher` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization, but may be an individual. The publisher (or steward) of the service definition is the organization or individual primarily responsible for the maintenance and upkeep of the service definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the service definition. This item SHOULD be populated unless the information is available from context.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.description
  l: extension-ServiceDefinition.description
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.description
  display:
    v: description
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.description` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.description` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This description can be used to capture details such as why the service definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the service definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile is presumed to be the predominant language in the place the profile was created).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.purpose
  l: extension-ServiceDefinition.purpose
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.purpose
  display:
    v: purpose
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.purpose` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.purpose` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element does not describe the usage of the service definition Instead it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this service definition.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.usage
  l: extension-ServiceDefinition.usage
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.usage
  display:
    v: usage
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.usage` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.usage` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.approvalDate
  l: extension-ServiceDefinition.approvalDate
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.approvalDate
  display:
    v: approvalDate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.approvalDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.approvalDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The 'date' element may be more recent than the approval date because of minor changes / editorial corrections.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.lastReviewDate
  l: extension-ServiceDefinition.lastReviewDate
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.lastReviewDate
  display:
    v: lastReviewDate
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.lastReviewDate` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.lastReviewDate` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If specified, this is usually after the approval date.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.effectivePeriod
  l: extension-ServiceDefinition.effectivePeriod
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.effectivePeriod
  display:
    v: effectivePeriod
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.effectivePeriod` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.effectivePeriod` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The effective period for a service definition determines when the content is applicable for usage and is independent of publication and review dates. For example, a measure intended to be used for the year 2016 might be published in 2015.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.useContext
  l: extension-ServiceDefinition.useContext
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.useContext
  display:
    v: useContext
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.useContext` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.jurisdiction
  l: extension-ServiceDefinition.jurisdiction
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.jurisdiction
  display:
    v: jurisdiction
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.jurisdiction` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.jurisdiction` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). It may be possible for the service definition to be used in jurisdictions other than those for which it was originally designed or intended.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.topic
  l: extension-ServiceDefinition.topic
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.topic
  display:
    v: topic
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.topic` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.topic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.contributor
  l: extension-ServiceDefinition.contributor
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.contributor
  display:
    v: contributor
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.contributor` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contributor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.contact
  l: extension-ServiceDefinition.contact
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.contact
  display:
    v: contact
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.contact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May be a web site, an email address, a telephone number, etc.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.copyright
  l: extension-ServiceDefinition.copyright
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.copyright
  display:
    v: copyright
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.copyright` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.copyright` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.relatedArtifact
  l: extension-ServiceDefinition.relatedArtifact
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.relatedArtifact
  display:
    v: relatedArtifact
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.relatedArtifact` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Each related resource is either an attachment, or a reference to another resource, but not both.

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.trigger
  l: extension-ServiceDefinition.trigger
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.trigger
  display:
    v: trigger
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.trigger` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.trigger` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.dataRequirement
  l: extension-ServiceDefinition.dataRequirement
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.dataRequirement
  display:
    v: dataRequirement
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.dataRequirement` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.dataRequirement` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).

source:
  v: http://hl7.org/fhir/StructureDefinition/ServiceDefinition
  l: ServiceDefinition
source version:
  v: 3.0.2
target:
  v: http://hl7.org/fhir/3.0/StructureDefinition/extension-ServiceDefinition.operationDefinition
  l: extension-ServiceDefinition.operationDefinition
target version:
  v: 0.1.0
element:
  code:
    v: ServiceDefinition.operationDefinition
  display:
    v: operationDefinition
  target:
    code:
      v: Extension
    equivalence:
      v: wider
    comment:
      v: Element `ServiceDefinition.operationDefinition` is not mapped to FHIR R4, since FHIR STU3 `ServiceDefinition` is not mapped. Element `ServiceDefinition.operationDefinition` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).