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

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

ConceptMap: R4BImplementationGuideElementMapToR5

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4B ImplementationGuide to FHIR R5.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to ImplementationGuideversion: 5.0.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.meta (meta)is equivalent toImplementationGuide.metaElement `ImplementationGuide.meta` is mapped to FHIR R5 element `ImplementationGuide.meta` as `Equivalent`.
ImplementationGuide.implicitRules (implicitRules)is equivalent toImplementationGuide.implicitRulesElement `ImplementationGuide.implicitRules` is mapped to FHIR R5 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 toImplementationGuide.languageElement `ImplementationGuide.language` is mapped to FHIR R5 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).
ImplementationGuide.text (text)is equivalent toImplementationGuide.textElement `ImplementationGuide.text` is mapped to FHIR R5 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.
ImplementationGuide.contained (contained)is equivalent toImplementationGuide.containedElement `ImplementationGuide.contained` is mapped to FHIR R5 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.
ImplementationGuide.url (url)is equivalent toImplementationGuide.urlElement `ImplementationGuide.url` is mapped to FHIR R5 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.
ImplementationGuide.version (version)is equivalent toImplementationGuide.versionElement `ImplementationGuide.version` is mapped to FHIR R5 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].
ImplementationGuide.name (name)is equivalent toImplementationGuide.nameElement `ImplementationGuide.name` is mapped to FHIR R5 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.
ImplementationGuide.title (title)is equivalent toImplementationGuide.titleElement `ImplementationGuide.title` is mapped to FHIR R5 element `ImplementationGuide.title` as `Equivalent`. This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.
ImplementationGuide.status (status)is equivalent toImplementationGuide.statusElement `ImplementationGuide.status` is mapped to FHIR R5 element `ImplementationGuide.status` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.
ImplementationGuide.experimental (experimental)is equivalent toImplementationGuide.experimentalElement `ImplementationGuide.experimental` is mapped to FHIR R5 element `ImplementationGuide.experimental` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.
ImplementationGuide.date (date)is equivalent toImplementationGuide.dateElement `ImplementationGuide.date` is mapped to FHIR R5 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.
ImplementationGuide.publisher (publisher)is equivalent toImplementationGuide.publisherElement `ImplementationGuide.publisher` is mapped to FHIR R5 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.
ImplementationGuide.contact (contact)is equivalent toImplementationGuide.contactElement `ImplementationGuide.contact` is mapped to FHIR R5 element `ImplementationGuide.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
ImplementationGuide.description (description)is equivalent toImplementationGuide.descriptionElement `ImplementationGuide.description` is mapped to FHIR R5 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).
ImplementationGuide.useContext (useContext)is equivalent toImplementationGuide.useContextElement `ImplementationGuide.useContext` is mapped to FHIR R5 element `ImplementationGuide.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
ImplementationGuide.jurisdiction (jurisdiction)is equivalent toImplementationGuide.jurisdictionElement `ImplementationGuide.jurisdiction` is mapped to FHIR R5 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.
ImplementationGuide.copyright (copyright)is equivalent toImplementationGuide.copyrightElement `ImplementationGuide.copyright` is mapped to FHIR R5 element `ImplementationGuide.copyright` as `Equivalent`.
ImplementationGuide.packageId (packageId)is equivalent toImplementationGuide.packageIdElement `ImplementationGuide.packageId` is mapped to FHIR R5 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.
ImplementationGuide.license (license)is equivalent toImplementationGuide.licenseElement `ImplementationGuide.license` is mapped to FHIR R5 element `ImplementationGuide.license` as `Equivalent`.
ImplementationGuide.fhirVersion (fhirVersion)is equivalent toImplementationGuide.fhirVersionElement `ImplementationGuide.fhirVersion` is mapped to FHIR R5 element `ImplementationGuide.fhirVersion` as `SourceIsNarrowerThanTarget`. The mappings for `ImplementationGuide.fhirVersion` do not allow expression of the necessary codes, per the bindings on the source and target. 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.
ImplementationGuide.dependsOn (dependsOn)is broader thanImplementationGuide.dependsOnElement `ImplementationGuide.dependsOn` is mapped to FHIR R5 element `ImplementationGuide.dependsOn` as `Equivalent`.
ImplementationGuide.dependsOn.uri (uri)is equivalent toImplementationGuide.dependsOn.uriElement `ImplementationGuide.dependsOn.uri` is mapped to FHIR R5 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.
ImplementationGuide.dependsOn.packageId (packageId)is equivalent toImplementationGuide.dependsOn.packageIdElement `ImplementationGuide.dependsOn.packageId` is mapped to FHIR R5 element `ImplementationGuide.dependsOn.packageId` as `Equivalent`.
ImplementationGuide.dependsOn.version (version)is equivalent toImplementationGuide.dependsOn.versionElement `ImplementationGuide.dependsOn.version` is mapped to FHIR R5 element `ImplementationGuide.dependsOn.version` as `Equivalent`. This follows the syntax of the NPM packaging version field - see [[reference]].
ImplementationGuide.global (global)is broader thanImplementationGuide.globalElement `ImplementationGuide.global` is mapped to FHIR R5 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.
ImplementationGuide.global.type (type)is broader thanImplementationGuide.global.typeElement `ImplementationGuide.global.type` is mapped to FHIR R5 element `ImplementationGuide.global.type` as `RelatedTo`. 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.
ImplementationGuide.global.profile (profile)is equivalent toImplementationGuide.global.profileElement `ImplementationGuide.global.profile` is mapped to FHIR R5 element `ImplementationGuide.global.profile` as `Equivalent`.
ImplementationGuide.definition (definition)is broader thanImplementationGuide.definitionElement `ImplementationGuide.definition` is mapped to FHIR R5 element `ImplementationGuide.definition` as `Equivalent`. Principally, this consists of information abuot source resource and file locations, and build parameters and templates.
ImplementationGuide.definition.grouping (grouping)is broader thanImplementationGuide.definition.groupingElement `ImplementationGuide.definition.grouping` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping` as `Equivalent`. Groupings are arbitrary sub-divisions of content. Typically, they are used to help build Table of Contents automatically.
ImplementationGuide.definition.grouping.name (name)is equivalent toImplementationGuide.definition.grouping.nameElement `ImplementationGuide.definition.grouping.name` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.name` as `Equivalent`.
ImplementationGuide.definition.grouping.description (description)is equivalent toImplementationGuide.definition.grouping.descriptionElement `ImplementationGuide.definition.grouping.description` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.description` as `Equivalent`.
ImplementationGuide.definition.resource (resource)is broader thanImplementationGuide.definition.resourceElement `ImplementationGuide.definition.resource` is mapped to FHIR R5 element `ImplementationGuide.definition.resource` as `Equivalent`.
ImplementationGuide.definition.resource.reference (reference)is equivalent toImplementationGuide.definition.resource.referenceElement `ImplementationGuide.definition.resource.reference` is mapped to FHIR R5 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.
ImplementationGuide.definition.resource.fhirVersion (fhirVersion)is equivalent toImplementationGuide.definition.resource.fhirVersionElement `ImplementationGuide.definition.resource.fhirVersion` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.fhirVersion` as `SourceIsNarrowerThanTarget`. The mappings for `ImplementationGuide.definition.resource.fhirVersion` do not allow expression of the necessary codes, per the bindings on the source and target. 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.
ImplementationGuide.definition.resource.name (name)is equivalent toImplementationGuide.definition.resource.nameElement `ImplementationGuide.definition.resource.name` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.name` as `Equivalent`.
ImplementationGuide.definition.resource.description (description)is equivalent toImplementationGuide.definition.resource.descriptionElement `ImplementationGuide.definition.resource.description` is mapped to FHIR R5 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).
ImplementationGuide.definition.resource.groupingId (groupingId)is equivalent toImplementationGuide.definition.resource.groupingIdElement `ImplementationGuide.definition.resource.groupingId` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.groupingId` as `Equivalent`. This must correspond to a package.id element within this implementation guide.
ImplementationGuide.definition.page (page)is broader thanImplementationGuide.definition.pageElement `ImplementationGuide.definition.page` is mapped to FHIR R5 element `ImplementationGuide.definition.page` as `Equivalent`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html.
ImplementationGuide.definition.page.name[x] (name[x])is broader thanImplementationGuide.definition.page.nameElement `ImplementationGuide.definition.page.name[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.page.name` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.definition.page.name[x]` do not cover the following types: Reference. The mappings for `ImplementationGuide.definition.page.name[x]` do not cover the following types based on type expansion: display, identifier, reference. The publishing tool will autogenerate source for list (source = n/a) and inject included implementations for include (source = uri of guide to include).
ImplementationGuide.definition.page.title (title)is equivalent toImplementationGuide.definition.page.titleElement `ImplementationGuide.definition.page.title` is mapped to FHIR R5 element `ImplementationGuide.definition.page.title` as `Equivalent`.
ImplementationGuide.definition.page.generation (generation)is equivalent toImplementationGuide.definition.page.generationElement `ImplementationGuide.definition.page.generation` is mapped to FHIR R5 element `ImplementationGuide.definition.page.generation` as `Equivalent`.
ImplementationGuide.definition.page.page (page)is equivalent toImplementationGuide.definition.page.pageElement `ImplementationGuide.definition.page.page` is mapped to FHIR R5 element `ImplementationGuide.definition.page.page` as `Equivalent`. The implementation guide breadcrumbs are generated from this structure.
ImplementationGuide.definition.parameter (parameter)is broader thanImplementationGuide.definition.parameterElement `ImplementationGuide.definition.parameter` is mapped to FHIR R5 element `ImplementationGuide.definition.parameter` as `Equivalent`.
ImplementationGuide.definition.parameter.code (code)is broader thanImplementationGuide.definition.parameter.codeElement `ImplementationGuide.definition.parameter.code` is mapped to FHIR R5 element `ImplementationGuide.definition.parameter.code` as `SourceIsNarrowerThanTarget`.
ImplementationGuide.definition.parameter.value (value)is equivalent toImplementationGuide.definition.parameter.valueElement `ImplementationGuide.definition.parameter.value` is mapped to FHIR R5 element `ImplementationGuide.definition.parameter.value` as `Equivalent`.
ImplementationGuide.definition.template (template)is broader thanImplementationGuide.definition.templateElement `ImplementationGuide.definition.template` is mapped to FHIR R5 element `ImplementationGuide.definition.template` as `Equivalent`.
ImplementationGuide.definition.template.code (code)is equivalent toImplementationGuide.definition.template.codeElement `ImplementationGuide.definition.template.code` is mapped to FHIR R5 element `ImplementationGuide.definition.template.code` as `Equivalent`.
ImplementationGuide.definition.template.source (source)is equivalent toImplementationGuide.definition.template.sourceElement `ImplementationGuide.definition.template.source` is mapped to FHIR R5 element `ImplementationGuide.definition.template.source` as `Equivalent`.
ImplementationGuide.definition.template.scope (scope)is equivalent toImplementationGuide.definition.template.scopeElement `ImplementationGuide.definition.template.scope` is mapped to FHIR R5 element `ImplementationGuide.definition.template.scope` as `Equivalent`.
ImplementationGuide.manifest (manifest)is broader thanImplementationGuide.manifestElement `ImplementationGuide.manifest` is mapped to FHIR R5 element `ImplementationGuide.manifest` as `Equivalent`.
ImplementationGuide.manifest.rendering (rendering)is equivalent toImplementationGuide.manifest.renderingElement `ImplementationGuide.manifest.rendering` is mapped to FHIR R5 element `ImplementationGuide.manifest.rendering` as `Equivalent`.
ImplementationGuide.manifest.resource (resource)is broader thanImplementationGuide.manifest.resourceElement `ImplementationGuide.manifest.resource` is mapped to FHIR R5 element `ImplementationGuide.manifest.resource` as `Equivalent`.
ImplementationGuide.manifest.resource.reference (reference)is equivalent toImplementationGuide.manifest.resource.referenceElement `ImplementationGuide.manifest.resource.reference` is mapped to FHIR R5 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.
ImplementationGuide.manifest.resource.relativePath (relativePath)is equivalent toImplementationGuide.manifest.resource.relativePathElement `ImplementationGuide.manifest.resource.relativePath` is mapped to FHIR R5 element `ImplementationGuide.manifest.resource.relativePath` as `Equivalent`. Appending 'rendering' + "/" + this should resolve to the resource page.
ImplementationGuide.manifest.page (page)is broader thanImplementationGuide.manifest.pageElement `ImplementationGuide.manifest.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `Equivalent`.
ImplementationGuide.manifest.page.name (name)is equivalent toImplementationGuide.manifest.page.nameElement `ImplementationGuide.manifest.page.name` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `Equivalent`. Appending 'rendering' + "/" + this should resolve to the page.
ImplementationGuide.manifest.page.title (title)is equivalent toImplementationGuide.manifest.page.titleElement `ImplementationGuide.manifest.page.title` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.title` as `Equivalent`.
ImplementationGuide.manifest.page.anchor (anchor)is equivalent toImplementationGuide.manifest.page.anchorElement `ImplementationGuide.manifest.page.anchor` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.anchor` as `Equivalent`. Appending 'rendering' + "/" + page.name + "#" + page.anchor should resolve to the anchor.
ImplementationGuide.manifest.image (image)is equivalent toImplementationGuide.manifest.imageElement `ImplementationGuide.manifest.image` is mapped to FHIR R5 element `ImplementationGuide.manifest.image` as `Equivalent`.
ImplementationGuide.manifest.other (other)is equivalent toImplementationGuide.manifest.otherElement `ImplementationGuide.manifest.other` is mapped to FHIR R5 element `ImplementationGuide.manifest.other` as `Equivalent`.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to R4B: type additional codesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.global.type (type)is equivalent toExtension (R4B: type additional codes)Element `ImplementationGuide.global.type` is mapped to FHIR R5 element `ImplementationGuide.global.type` as `RelatedTo`. 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.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to R4B: Is an example/What is this an example of? (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.definition.resource.example[x] (example[x])is broader thanExtension (R4B: Is an example/What is this an example of? (new))Element `ImplementationGuide.definition.resource.example[x]` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.resource.example[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Examples: * StructureDefinition -> Any * ValueSet -> expansion * OperationDefinition -> Parameters * Questionnaire -> QuestionnaireResponse.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to R4B: Where to find that page additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.definition.page.name[x] (name[x])is broader thanExtension (R4B: Where to find that page additional types)Element `ImplementationGuide.definition.page.name[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.page.name` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.definition.page.name[x]` do not cover the following types: Reference. The mappings for `ImplementationGuide.definition.page.name[x]` do not cover the following types based on type expansion: display, identifier, reference. The publishing tool will autogenerate source for list (source = n/a) and inject included implementations for include (source = uri of guide to include).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to R4B: apply | path-resource | path-pages | path-tx-cache | expansion-parameter | rule-broken-links | generate-xml | generate-json | generate-turtle | html-templateversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.definition.parameter.code (code)is equivalent toExtension (R4B: apply | path-resource | path-pages | path-tx-cache | expansion-parameter | rule-broken-links | generate-xml | generate-json | generate-turtle | html-template)Element `ImplementationGuide.definition.parameter.code` is mapped to FHIR R5 element `ImplementationGuide.definition.parameter.code` as `SourceIsNarrowerThanTarget`.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.3.0 to R4B: Is an example/What is this an example of? (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.manifest.resource.example[x] (example[x])is broader thanExtension (R4B: Is an example/What is this an example of? (new))Element `ImplementationGuide.manifest.resource.example[x]` has a context of ImplementationGuide.manifest.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.resource.example[x]` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). 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.