R4B-ImplementationGuide-element-map-to-R4
type: ConceptMap
node role: treeRoot
id:
  v: R4B-ImplementationGuide-element-map-to-R4
text:
  status:
    v: generated
  div:
    v: Generated Narrative: ConceptMap R4B-ImplementationGuide-element-map-to-R4 Mapping from http://hl7.org/fhir/4.3 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to ImplementationGuideversion: 4.0.1) Source Code Relationship Target Code Comment ImplementationGuide.meta (meta) is equivalent to ImplementationGuide.meta Element `ImplementationGuide.meta` is mapped to FHIR R4 element `ImplementationGuide.meta` as `Equivalent`. ImplementationGuide.implicitRules (implicitRules) is equivalent to ImplementationGuide.implicitRules Element `ImplementationGuide.implicitRules` is mapped to FHIR R4 element `ImplementationGuide.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. ImplementationGuide.language (language) is equivalent to ImplementationGuide.language Element `ImplementationGuide.language` is mapped to FHIR R4 element `ImplementationGuide.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 …
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-r4b.r4
        l: hl7.fhir.uv.xver-r4b.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-r4b.r4
        l: hl7.fhir.uv.xver-r4b.r4
url:
  v: http://hl7.org/fhir/uv/xver/ConceptMap/R4B-ImplementationGuide-element-map-to-R4
  l: R4B-ImplementationGuide-element-map-to-R4
version:
  v: 0.1.0
name:
  v: R4BImplementationGuideElementMapToR4
title:
  v: Cross-version mapping for FHIR R4B ImplementationGuide to FHIR R4 ImplementationGuide
status:
  v: active
experimental:
  v: false
date:
  v: 2026-03-17T16:03:46.8711685-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 R4B ImplementationGuide 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/4.3
  l: http://hl7.org/fhir/4.3
target: Uri
  v: http://hl7.org/fhir/4.0
  l: http://hl7.org/fhir/4.0
group:
  source:
    v: http://hl7.org/fhir/StructureDefinition/ImplementationGuide
    l: ImplementationGuide
  source version:
    v: 4.3.0
  target:
    v: http://hl7.org/fhir/StructureDefinition/ImplementationGuide
    l: ImplementationGuide
  target version:
    v: 4.0.1
  element:
    code:
      v: ImplementationGuide.meta
    display:
      v: meta
    target:
      code:
        v: ImplementationGuide.meta
      display:
        v: ImplementationGuide.meta
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.meta` is mapped to FHIR R4 element `ImplementationGuide.meta` as `Equivalent`.
  element:
    code:
      v: ImplementationGuide.implicitRules
    display:
      v: implicitRules
    target:
      code:
        v: ImplementationGuide.implicitRules
      display:
        v: ImplementationGuide.implicitRules
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.implicitRules` is mapped to FHIR R4 element `ImplementationGuide.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.
  element:
    code:
      v: ImplementationGuide.language
    display:
      v: language
    target:
      code:
        v: ImplementationGuide.language
      display:
        v: ImplementationGuide.language
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.language` is mapped to FHIR R4 element `ImplementationGuide.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).
  element:
    code:
      v: ImplementationGuide.text
    display:
      v: text
    target:
      code:
        v: ImplementationGuide.text
      display:
        v: ImplementationGuide.text
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.text` is mapped to FHIR R4 element `ImplementationGuide.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.
  element:
    code:
      v: ImplementationGuide.contained
    display:
      v: contained
    target:
      code:
        v: ImplementationGuide.contained
      display:
        v: ImplementationGuide.contained
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.contained` is mapped to FHIR R4 element `ImplementationGuide.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.
  element:
    code:
      v: ImplementationGuide.url
    display:
      v: url
    target:
      code:
        v: ImplementationGuide.url
      display:
        v: ImplementationGuide.url
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.url` is mapped to FHIR R4 element `ImplementationGuide.url` as `Equivalent`. 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. The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in [Technical and Business Versions](https://hl7.org/fhir/resource..html#versions). In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the [meta.source](https://hl7.org/fhir/resou.html#meta) element to indicate where the current master source of the resource can be found.
  element:
    code:
      v: ImplementationGuide.version
    display:
      v: version
    target:
      code:
        v: ImplementationGuide.version
      display:
        v: ImplementationGuide.version
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.version` is mapped to FHIR R4 element `ImplementationGuide.version` as `Equivalent`. There may be different implementation guide instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the implementation guide with the format [url]|[version].
  element:
    code:
      v: ImplementationGuide.name
    display:
      v: name
    target:
      code:
        v: ImplementationGuide.name
      display:
        v: ImplementationGuide.name
      equivalence:
        v: equivalent
      comment:
        v: Element `ImplementationGuide.name` is mapped to FHIR R4 element `ImplementationGuide.name` as `Equivalent`. The name is not expected to be globally unique. The name should be a simple alphanumeric type name to ensure that it is machine-processing friendly.

code:
  v: ImplementationGuide.title
display:
  v: title
target:
  code:
    v: ImplementationGuide.title
  display:
    v: ImplementationGuide.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.title` is mapped to FHIR R4 element `ImplementationGuide.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

code:
  v: ImplementationGuide.status
display:
  v: status
target:
  code:
    v: ImplementationGuide.status
  display:
    v: ImplementationGuide.status
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.status` is mapped to FHIR R4 element `ImplementationGuide.status` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.

code:
  v: ImplementationGuide.experimental
display:
  v: experimental
target:
  code:
    v: ImplementationGuide.experimental
  display:
    v: ImplementationGuide.experimental
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.experimental` is mapped to FHIR R4 element `ImplementationGuide.experimental` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.

code:
  v: ImplementationGuide.date
display:
  v: date
target:
  code:
    v: ImplementationGuide.date
  display:
    v: ImplementationGuide.date
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.date` is mapped to FHIR R4 element `ImplementationGuide.date` as `Equivalent`. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the implementation guide. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

code:
  v: ImplementationGuide.publisher
display:
  v: publisher
target:
  code:
    v: ImplementationGuide.publisher
  display:
    v: ImplementationGuide.publisher
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.publisher` is mapped to FHIR R4 element `ImplementationGuide.publisher` as `Equivalent`. Usually an organization but may be an individual. The publisher (or steward) of the implementation guide is the organization or individual primarily responsible for the maintenance and upkeep of the implementation guide. 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 implementation guide. This item SHOULD be populated unless the information is available from context.

code:
  v: ImplementationGuide.contact
display:
  v: contact
target:
  code:
    v: ImplementationGuide.contact
  display:
    v: ImplementationGuide.contact
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.contact` is mapped to FHIR R4 element `ImplementationGuide.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.

code:
  v: ImplementationGuide.description
display:
  v: description
target:
  code:
    v: ImplementationGuide.description
  display:
    v: ImplementationGuide.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.description` is mapped to FHIR R4 element `ImplementationGuide.description` as `Equivalent`. This description can be used to capture details such as why the implementation guide 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 implementation guide 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 implementation guide is presumed to be the predominant language in the place the implementation guide was created).

code:
  v: ImplementationGuide.useContext
display:
  v: useContext
target:
  code:
    v: ImplementationGuide.useContext
  display:
    v: ImplementationGuide.useContext
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.useContext` is mapped to FHIR R4 element `ImplementationGuide.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.

code:
  v: ImplementationGuide.jurisdiction
display:
  v: jurisdiction
target:
  code:
    v: ImplementationGuide.jurisdiction
  display:
    v: ImplementationGuide.jurisdiction
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.jurisdiction` is mapped to FHIR R4 element `ImplementationGuide.jurisdiction` as `Equivalent`. It may be possible for the implementation guide to be used in jurisdictions other than those for which it was originally designed or intended.

code:
  v: ImplementationGuide.copyright
display:
  v: copyright
target:
  code:
    v: ImplementationGuide.copyright
  display:
    v: ImplementationGuide.copyright
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.copyright` is mapped to FHIR R4 element `ImplementationGuide.copyright` as `Equivalent`.

code:
  v: ImplementationGuide.packageId
display:
  v: packageId
target:
  code:
    v: ImplementationGuide.packageId
  display:
    v: ImplementationGuide.packageId
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.packageId` is mapped to FHIR R4 element `ImplementationGuide.packageId` as `Equivalent`. Many (if not all) IG publishing tools will require that this element be present. For implementation guides published through HL7 or the FHIR foundation, the FHIR product director assigns package IDs.

code:
  v: ImplementationGuide.license
display:
  v: license
target:
  code:
    v: ImplementationGuide.license
  display:
    v: ImplementationGuide.license
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.license` is mapped to FHIR R4 element `ImplementationGuide.license` as `Equivalent`.

code:
  v: ImplementationGuide.fhirVersion
display:
  v: fhirVersion
target:
  code:
    v: ImplementationGuide.fhirVersion
  display:
    v: ImplementationGuide.fhirVersion
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.fhirVersion` is mapped to FHIR R4 element `ImplementationGuide.fhirVersion` as `SourceIsBroaderThanTarget`. Most implementation guides target a single version - e.g. they describe how to use a particular version, and the profiles and examples etc are valid for that version. But some implementation guides describe how to use multiple different versions of FHIR to solve the same problem, or in concert with each other. Typically, the requirement to support multiple versions arises as implementation matures and different implementation communities are stuck at different versions by regulation or market dynamics.

code:
  v: ImplementationGuide.dependsOn
display:
  v: dependsOn
target:
  code:
    v: ImplementationGuide.dependsOn
  display:
    v: ImplementationGuide.dependsOn
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.dependsOn` is mapped to FHIR R4 element `ImplementationGuide.dependsOn` as `Equivalent`.

code:
  v: ImplementationGuide.dependsOn.uri
display:
  v: uri
target:
  code:
    v: ImplementationGuide.dependsOn.uri
  display:
    v: ImplementationGuide.dependsOn.uri
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.dependsOn.uri` is mapped to FHIR R4 element `ImplementationGuide.dependsOn.uri` as `Equivalent`. Usually, A canonical reference to the implementation guide is the same as the master location at which the implementation guide is published.

code:
  v: ImplementationGuide.dependsOn.packageId
display:
  v: packageId
target:
  code:
    v: ImplementationGuide.dependsOn.packageId
  display:
    v: ImplementationGuide.dependsOn.packageId
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.dependsOn.packageId` is mapped to FHIR R4 element `ImplementationGuide.dependsOn.packageId` as `Equivalent`.

code:
  v: ImplementationGuide.dependsOn.version
display:
  v: version
target:
  code:
    v: ImplementationGuide.dependsOn.version
  display:
    v: ImplementationGuide.dependsOn.version
  equivalence:
    v: equivalent
  comment:
v: Element `ImplementationGuide.dependsOn.version` is mapped to FHIR R4 element `ImplementationGuide.dependsOn.version` as `Equivalent`. This follows the syntax of the NPM packaging version field - see reference.

code:
  v: ImplementationGuide.global
display:
  v: global
target:
  code:
    v: ImplementationGuide.global
  display:
    v: ImplementationGuide.global
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.global` is mapped to FHIR R4 element `ImplementationGuide.global` as `Equivalent`. See [Default Profiles](https://hl7.org/fhir/implemen.html#default) for a discussion of which resources are 'covered' by an implementation guide.

code:
  v: ImplementationGuide.global.type
display:
  v: type
target:
  code:
    v: ImplementationGuide.global.type
  display:
    v: ImplementationGuide.global.type
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.global.type` is mapped to FHIR R4 element `ImplementationGuide.global.type` as `SourceIsNarrowerThanTarget`. The mappings for `ImplementationGuide.global.type` do not allow expression of the necessary codes, per the bindings on the source and target. The type must match that of the profile that is referred to but is made explicit here as a denormalization so that a system processing the implementation guide resource knows which resources the profile applies to even if the profile itself is not available.

code:
  v: ImplementationGuide.global.profile
display:
  v: profile
target:
  code:
    v: ImplementationGuide.global.profile
  display:
    v: ImplementationGuide.global.profile
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.global.profile` is mapped to FHIR R4 element `ImplementationGuide.global.profile` as `Equivalent`.

code:
  v: ImplementationGuide.definition
display:
  v: definition
target:
  code:
    v: ImplementationGuide.definition
  display:
    v: ImplementationGuide.definition
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition` is mapped to FHIR R4 element `ImplementationGuide.definition` as `Equivalent`. Principally, this consists of information abuot source resource and file locations, and build parameters and templates.

code:
  v: ImplementationGuide.definition.grouping
display:
  v: grouping
target:
  code:
    v: ImplementationGuide.definition.grouping
  display:
    v: ImplementationGuide.definition.grouping
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.grouping` is mapped to FHIR R4 element `ImplementationGuide.definition.grouping` as `Equivalent`. Groupings are arbitrary sub-divisions of content. Typically, they are used to help build Table of Contents automatically.

code:
  v: ImplementationGuide.definition.grouping.name
display:
  v: name
target:
  code:
    v: ImplementationGuide.definition.grouping.name
  display:
    v: ImplementationGuide.definition.grouping.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.grouping.name` is mapped to FHIR R4 element `ImplementationGuide.definition.grouping.name` as `Equivalent`.

code:
  v: ImplementationGuide.definition.grouping.description
display:
  v: description
target:
  code:
    v: ImplementationGuide.definition.grouping.description
  display:
    v: ImplementationGuide.definition.grouping.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.grouping.description` is mapped to FHIR R4 element `ImplementationGuide.definition.grouping.description` as `Equivalent`.

code:
  v: ImplementationGuide.definition.resource
display:
  v: resource
target:
  code:
    v: ImplementationGuide.definition.resource
  display:
    v: ImplementationGuide.definition.resource
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.resource` is mapped to FHIR R4 element `ImplementationGuide.definition.resource` as `Equivalent`.

code:
  v: ImplementationGuide.definition.resource.reference
display:
  v: reference
target:
  code:
    v: ImplementationGuide.definition.resource.reference
  display:
    v: ImplementationGuide.definition.resource.reference
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.resource.reference` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.reference` as `Equivalent`. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

code:
  v: ImplementationGuide.definition.resource.fhirVersion
display:
  v: fhirVersion
target:
  code:
    v: ImplementationGuide.definition.resource.fhirVersion
  display:
    v: ImplementationGuide.definition.resource.fhirVersion
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.resource.fhirVersion` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.fhirVersion` as `SourceIsBroaderThanTarget`. The resource SHALL be valid against all the versions it is specified to apply to. If the resource referred to is a StructureDefinition, the fhirVersion stated in the StructureDefinition cannot disagree with the version specified here; the specified versions SHALL include the version specified by the StructureDefinition, and may include additional versions using the [applicable-version](https://hl7.org/fhir/extension-structuredefinition-applicable-version.html) extension.

code:
  v: ImplementationGuide.definition.resource.name
display:
  v: name
target:
  code:
    v: ImplementationGuide.definition.resource.name
  display:
    v: ImplementationGuide.definition.resource.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.resource.name` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.name` as `Equivalent`.

code:
  v: ImplementationGuide.definition.resource.description
display:
  v: description
target:
  code:
    v: ImplementationGuide.definition.resource.description
  display:
    v: ImplementationGuide.definition.resource.description
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.resource.description` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.description` as `Equivalent`. This is mostly used with examples to explain why it is present (though they can have extensive comments in the examples).

code:
  v: ImplementationGuide.definition.resource.example[x]
display:
  v: example[x]
target:
  code:
    v: ImplementationGuide.definition.resource.example[x]
  display:
    v: ImplementationGuide.definition.resource.example[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.example[x]` as `Equivalent`. The target context `ImplementationGuide.definition.resource.example[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ImplementationGuide.definition.resource`. Examples: * StructureDefinition -> Any * ValueSet -> expansion * OperationDefinition -> Parameters * Questionnaire -> QuestionnaireResponse.

code:
  v: ImplementationGuide.definition.resource.groupingId
display:
  v: groupingId
target:
  code:
    v: ImplementationGuide.definition.resource.groupingId
  display:
    v: ImplementationGuide.definition.resource.groupingId
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.resource.groupingId` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.groupingId` as `Equivalent`. This must correspond to a package.id element within this implementation guide.

code:
  v: ImplementationGuide.definition.page
display:
  v: page
target:
  code:
    v: ImplementationGuide.definition.page
  display:
    v: ImplementationGuide.definition.page
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.page` is mapped to FHIR R4 element `ImplementationGuide.definition.page` as `Equivalent`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html.

code:
  v: ImplementationGuide.definition.page.name[x]
display:
  v: name[x]
target:
  code:
    v: ImplementationGuide.definition.page.name[x]
  display:
    v: ImplementationGuide.definition.page.name[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.page.name[x]` is mapped to FHIR R4 element `ImplementationGuide.definition.page.name[x]` as `Equivalent`. The target context `ImplementationGuide.definition.page.name[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ImplementationGuide.definition.page`. The publishing tool will autogenerate source for list (source = n/a) and inject included implementations for include (source = uri of guide to include).

code:
  v: ImplementationGuide.definition.page.title
display:
  v: title
target:
  code:
    v: ImplementationGuide.definition.page.title
  display:
    v: ImplementationGuide.definition.page.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.page.title` is mapped to FHIR R4 element `ImplementationGuide.definition.page.title` as `Equivalent`.

code:
  v: ImplementationGuide.definition.page.generation
display:
  v: generation
target:
  code:
    v: ImplementationGuide.definition.page.generation
  display:
    v: ImplementationGuide.definition.page.generation
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.page.generation` is mapped to FHIR R4 element `ImplementationGuide.definition.page.generation` as `Equivalent`.

code:
  v: ImplementationGuide.definition.page.page
display:
  v: page
target:
  code:
    v: ImplementationGuide.definition.page.page
  display:
    v: ImplementationGuide.definition.page.page
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.page.page` is mapped to FHIR R4 element `ImplementationGuide.definition.page.page` as `Equivalent`. The implementation guide breadcrumbs are generated from this structure.

code:
  v: ImplementationGuide.definition.parameter
display:
  v: parameter
target:
  code:
    v: ImplementationGuide.definition.parameter
  display:
    v: ImplementationGuide.definition.parameter
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.parameter` is mapped to FHIR R4 element `ImplementationGuide.definition.parameter` as `Equivalent`.

code:
  v: ImplementationGuide.definition.parameter.code
display:
  v: code
target:
  code:
    v: ImplementationGuide.definition.parameter.code
  display:
    v: ImplementationGuide.definition.parameter.code
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.parameter.code` is mapped to FHIR R4 element `ImplementationGuide.definition.parameter.code` as `Equivalent`.

code:
  v: ImplementationGuide.definition.parameter.value
display:
  v: value
target:
  code:
    v: ImplementationGuide.definition.parameter.value
  display:
    v: ImplementationGuide.definition.parameter.value
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.parameter.value` is mapped to FHIR R4 element `ImplementationGuide.definition.parameter.value` as `Equivalent`.

code:
  v: ImplementationGuide.definition.template
display:
  v: template
target:
  code:
    v: ImplementationGuide.definition.template
  display:
    v: ImplementationGuide.definition.template
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.definition.template` is mapped to FHIR R4 element `ImplementationGuide.definition.template` as `Equivalent`.

code:
  v: ImplementationGuide.definition.template.code
display:
  v: code
target:
  code:
    v: ImplementationGuide.definition.template.code
  display:
    v: ImplementationGuide.definition.template.code
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.template.code` is mapped to FHIR R4 element `ImplementationGuide.definition.template.code` as `Equivalent`.

code:
  v: ImplementationGuide.definition.template.source
display:
  v: source
target:
  code:
    v: ImplementationGuide.definition.template.source
  display:
    v: ImplementationGuide.definition.template.source
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.template.source` is mapped to FHIR R4 element `ImplementationGuide.definition.template.source` as `Equivalent`.

code:
  v: ImplementationGuide.definition.template.scope
display:
  v: scope
target:
  code:
    v: ImplementationGuide.definition.template.scope
  display:
    v: ImplementationGuide.definition.template.scope
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.definition.template.scope` is mapped to FHIR R4 element `ImplementationGuide.definition.template.scope` as `Equivalent`.

code:
  v: ImplementationGuide.manifest
display:
  v: manifest
target:
  code:
    v: ImplementationGuide.manifest
  display:
    v: ImplementationGuide.manifest
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.manifest` is mapped to FHIR R4 element `ImplementationGuide.manifest` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.rendering
display:
  v: rendering
target:
  code:
    v: ImplementationGuide.manifest.rendering
  display:
    v: ImplementationGuide.manifest.rendering
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.rendering` is mapped to FHIR R4 element `ImplementationGuide.manifest.rendering` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.resource
display:
  v: resource
target:
  code:
    v: ImplementationGuide.manifest.resource
  display:
    v: ImplementationGuide.manifest.resource
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.manifest.resource` is mapped to FHIR R4 element `ImplementationGuide.manifest.resource` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.resource.reference
display:
  v: reference
target:
  code:
    v: ImplementationGuide.manifest.resource.reference
  display:
    v: ImplementationGuide.manifest.resource.reference
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.resource.reference` is mapped to FHIR R4 element `ImplementationGuide.manifest.resource.reference` as `Equivalent`. Usually this is a relative URL that locates the resource within the implementation guide. If you authoring an implementation guide, and will publish it using the FHIR publication tooling, use a URI that may point to a resource, or to one of various alternative representations (e.g. spreadsheet). The tooling will convert this when it publishes it.

code:
  v: ImplementationGuide.manifest.resource.example[x]
display:
  v: example[x]
target:
  code:
    v: ImplementationGuide.manifest.resource.example[x]
  display:
    v: ImplementationGuide.manifest.resource.example[x]
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.resource.example[x]` is mapped to FHIR R4 element `ImplementationGuide.manifest.resource.example[x]` as `Equivalent`. The target context `ImplementationGuide.manifest.resource.example[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ImplementationGuide.manifest.resource`. Typically, conformance resources and knowledge resources are directly part of the implementation guide, with their normal meaning, and patient linked resources are usually examples. However this is not always true.

code:
  v: ImplementationGuide.manifest.resource.relativePath
display:
  v: relativePath
target:
  code:
    v: ImplementationGuide.manifest.resource.relativePath
  display:
    v: ImplementationGuide.manifest.resource.relativePath
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.resource.relativePath` is mapped to FHIR R4 element `ImplementationGuide.manifest.resource.relativePath` as `Equivalent`. Appending 'rendering' + "/" + this should resolve to the resource page.

code:
  v: ImplementationGuide.manifest.page
display:
  v: page
target:
  code:
    v: ImplementationGuide.manifest.page
  display:
    v: ImplementationGuide.manifest.page
  equivalence:
    v: wider
  comment:
    v: Element `ImplementationGuide.manifest.page` is mapped to FHIR R4 element `ImplementationGuide.manifest.page` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.page.name
display:
  v: name
target:
  code:
    v: ImplementationGuide.manifest.page.name
  display:
    v: ImplementationGuide.manifest.page.name
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.page.name` is mapped to FHIR R4 element `ImplementationGuide.manifest.page.name` as `Equivalent`. Appending 'rendering' + "/" + this should resolve to the page.

code:
  v: ImplementationGuide.manifest.page.title
display:
  v: title
target:
  code:
    v: ImplementationGuide.manifest.page.title
  display:
    v: ImplementationGuide.manifest.page.title
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.page.title` is mapped to FHIR R4 element `ImplementationGuide.manifest.page.title` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.page.anchor
display:
  v: anchor
target:
  code:
    v: ImplementationGuide.manifest.page.anchor
  display:
    v: ImplementationGuide.manifest.page.anchor
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.page.anchor` is mapped to FHIR R4 element `ImplementationGuide.manifest.page.anchor` as `Equivalent`. Appending 'rendering' + "/" + page.name + "#" + page.anchor should resolve to the anchor.

code:
  v: ImplementationGuide.manifest.image
display:
  v: image
target:
  code:
    v: ImplementationGuide.manifest.image
  display:
    v: ImplementationGuide.manifest.image
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.image` is mapped to FHIR R4 element `ImplementationGuide.manifest.image` as `Equivalent`.

code:
  v: ImplementationGuide.manifest.other
display:
  v: other
target:
  code:
    v: ImplementationGuide.manifest.other
  display:
    v: ImplementationGuide.manifest.other
  equivalence:
    v: equivalent
  comment:
    v: Element `ImplementationGuide.manifest.other` is mapped to FHIR R4 element `ImplementationGuide.manifest.other` as `Equivalent`.

source:
  v: http://hl7.org/fhir/StructureDefinition/ImplementationGuide
  l: ImplementationGuide
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ImplementationGuide.fhirVersion
  l: extension-ImplementationGuide.fhirVersion
target version:
  v: 0.1.0
element:
  code:
    v: ImplementationGuide.fhirVersion
  display:
    v: fhirVersion
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ImplementationGuide.fhirVersion` is mapped to FHIR R4 element `ImplementationGuide.fhirVersion` as `SourceIsBroaderThanTarget`. Most implementation guides target a single version - e.g. they describe how to use a particular version, and the profiles and examples etc are valid for that version. But some implementation guides describe how to use multiple different versions of FHIR to solve the same problem, or in concert with each other. Typically, the requirement to support multiple versions arises as implementation matures and different implementation communities are stuck at different versions by regulation or market dynamics.

source:
  v: http://hl7.org/fhir/StructureDefinition/ImplementationGuide
  l: ImplementationGuide
source version:
  v: 4.3.0
target:
  v: http://hl7.org/fhir/4.3/StructureDefinition/extension-ImplementationGuide.definition.resource.fhirVersion
  l: extension-ImplementationGuide.definition.resource.fhirVersion
target version:
  v: 0.1.0
element:
  code:
    v: ImplementationGuide.definition.resource.fhirVersion
  display:
    v: fhirVersion
  target:
    code:
      v: Extension
    equivalence:
      v: equivalent
    comment:
      v: Element `ImplementationGuide.definition.resource.fhirVersion` is mapped to FHIR R4 element `ImplementationGuide.definition.resource.fhirVersion` as `SourceIsBroaderThanTarget`. The resource SHALL be valid against all the versions it is specified to apply to. If the resource referred to is a StructureDefinition, the fhirVersion stated in the StructureDefinition cannot disagree with the version specified here; the specified versions SHALL include the version specified by the StructureDefinition, and may include additional versions using the [applicable-version](https://hl7.org/fhir/extension-structuredefinition-applicable-version.html) extension.