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

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

ConceptMap: R4ImplementationGuideElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4 ImplementationGuide to FHIR STU3.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1Codes from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2
ImplementationGuide.metametais equivalent toImplementationGuide.metaImplementationGuide.metaElement `ImplementationGuide.meta` is mapped to FHIR STU3 element `ImplementationGuide.meta` as `Equivalent`.
ImplementationGuide.implicitRulesimplicitRulesis equivalent toImplementationGuide.implicitRulesImplementationGuide.implicitRulesElement `ImplementationGuide.implicitRules` is mapped to FHIR STU3 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.languagelanguageis equivalent toImplementationGuide.languageImplementationGuide.languageElement `ImplementationGuide.language` is mapped to FHIR STU3 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.texttextis equivalent toImplementationGuide.textImplementationGuide.textElement `ImplementationGuide.text` is mapped to FHIR STU3 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.containedcontainedis equivalent toImplementationGuide.containedImplementationGuide.containedElement `ImplementationGuide.contained` is mapped to FHIR STU3 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.urlurlis equivalent toImplementationGuide.urlImplementationGuide.urlElement `ImplementationGuide.url` is mapped to FHIR STU3 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.versionversionis equivalent toImplementationGuide.versionImplementationGuide.versionElement `ImplementationGuide.version` is mapped to FHIR STU3 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.namenameis equivalent toImplementationGuide.nameImplementationGuide.nameElement `ImplementationGuide.name` is mapped to FHIR STU3 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.statusstatusis equivalent toImplementationGuide.statusImplementationGuide.statusElement `ImplementationGuide.status` is mapped to FHIR STU3 element `ImplementationGuide.status` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.
ImplementationGuide.experimentalexperimentalis equivalent toImplementationGuide.experimentalImplementationGuide.experimentalElement `ImplementationGuide.experimental` is mapped to FHIR STU3 element `ImplementationGuide.experimental` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use versus not.
ImplementationGuide.datedateis equivalent toImplementationGuide.dateImplementationGuide.dateElement `ImplementationGuide.date` is mapped to FHIR STU3 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.publisherpublisheris equivalent toImplementationGuide.publisherImplementationGuide.publisherElement `ImplementationGuide.publisher` is mapped to FHIR STU3 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.contactcontactis equivalent toImplementationGuide.contactImplementationGuide.contactElement `ImplementationGuide.contact` is mapped to FHIR STU3 element `ImplementationGuide.contact` as `Equivalent`. May be a web site, an email address, a telephone number, etc.
ImplementationGuide.descriptiondescriptionis equivalent toImplementationGuide.descriptionImplementationGuide.descriptionElement `ImplementationGuide.description` is mapped to FHIR STU3 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.useContextuseContextis equivalent toImplementationGuide.useContextImplementationGuide.useContextElement `ImplementationGuide.useContext` is mapped to FHIR STU3 element `ImplementationGuide.useContext` as `Equivalent`. When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
ImplementationGuide.jurisdictionjurisdictionis equivalent toImplementationGuide.jurisdictionImplementationGuide.jurisdictionElement `ImplementationGuide.jurisdiction` is mapped to FHIR STU3 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.copyrightcopyrightis equivalent toImplementationGuide.copyrightImplementationGuide.copyrightElement `ImplementationGuide.copyright` is mapped to FHIR STU3 element `ImplementationGuide.copyright` as `Equivalent`.
ImplementationGuide.fhirVersionfhirVersionmaps to wider conceptImplementationGuide.fhirVersionImplementationGuide.fhirVersionElement `ImplementationGuide.fhirVersion` is mapped to FHIR STU3 element `ImplementationGuide.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.fhirVersion` do not cover the following types: code. The mappings for `ImplementationGuide.fhirVersion` do not cover the following types based on type expansion: value. 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.dependsOndependsOnmaps to wider conceptImplementationGuide.dependencyImplementationGuide.dependencyElement `ImplementationGuide.dependsOn` is mapped to FHIR STU3 element `ImplementationGuide.dependency` as `Equivalent`.
ImplementationGuide.dependsOn.uriuriis equivalent toImplementationGuide.dependency.uriImplementationGuide.dependency.uriElement `ImplementationGuide.dependsOn.uri` is mapped to FHIR STU3 element `ImplementationGuide.dependency.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.packageIdpackageIdnarrowerImplementationGuide.dependencyImplementationGuide.dependencyElement `ImplementationGuide.dependsOn.packageId` is mapped to FHIR STU3 element `ImplementationGuide.dependency` as `SourceIsNarrowerThanTarget`.
ImplementationGuide.dependsOn.versionversionnarrowerImplementationGuide.dependencyImplementationGuide.dependencyElement `ImplementationGuide.dependsOn.version` is mapped to FHIR STU3 element `ImplementationGuide.dependency` as `SourceIsNarrowerThanTarget`. This follows the syntax of the NPM packaging version field - see [[reference]].
ImplementationGuide.globalglobalmaps to wider conceptImplementationGuide.globalImplementationGuide.globalElement `ImplementationGuide.global` is mapped to FHIR STU3 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.typetypemaps to wider conceptImplementationGuide.global.typeImplementationGuide.global.typeElement `ImplementationGuide.global.type` is mapped to FHIR STU3 element `ImplementationGuide.global.type` as `SourceIsBroaderThanTarget`. 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.profileprofilemaps to wider conceptImplementationGuide.global.profileImplementationGuide.global.profileElement `ImplementationGuide.global.profile` is mapped to FHIR STU3 element `ImplementationGuide.global.profile` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.global.profile` do not cover the following types: canonical. The mappings for `ImplementationGuide.global.profile` do not cover the following types based on type expansion: value.
ImplementationGuide.definition.groupinggroupingmaps to wider conceptImplementationGuide.packageImplementationGuide.packageElement `ImplementationGuide.definition.grouping` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.grouping` is mapped to FHIR STU3 element `ImplementationGuide.package` as `Equivalent`. Groupings are arbitrary sub-divisions of content. Typically, they are used to help build Table of Contents automatically.
ImplementationGuide.definition.grouping.namenameis equivalent toImplementationGuide.package.nameImplementationGuide.package.nameElement `ImplementationGuide.definition.grouping.name` is part of an existing definition because parent element `ImplementationGuide.definition.grouping` requires a cross-version extension. Element `ImplementationGuide.definition.grouping.name` is mapped to FHIR STU3 element `ImplementationGuide.package.name` as `Equivalent`.
ImplementationGuide.definition.grouping.descriptiondescriptionis equivalent toImplementationGuide.package.descriptionImplementationGuide.package.descriptionElement `ImplementationGuide.definition.grouping.description` is part of an existing definition because parent element `ImplementationGuide.definition.grouping` requires a cross-version extension. Element `ImplementationGuide.definition.grouping.description` is mapped to FHIR STU3 element `ImplementationGuide.package.description` as `Equivalent`.
ImplementationGuide.definition.resourceresourcemaps to wider conceptImplementationGuide.package.resourceImplementationGuide.package.resourceElement `ImplementationGuide.definition.resource` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.resource` is mapped to FHIR STU3 element `ImplementationGuide.package.resource` as `Equivalent`.
ImplementationGuide.definition.resource.referencereferenceis equivalent toImplementationGuide.package.resource.source[x]ImplementationGuide.package.resource.source[x]Element `ImplementationGuide.definition.resource.reference` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.reference` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.source[x]` as `Equivalent`. The target context `ImplementationGuide.package.resource.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ImplementationGuide.package.resource`. 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.namenameis equivalent toImplementationGuide.package.resource.nameImplementationGuide.package.resource.nameElement `ImplementationGuide.definition.resource.name` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.name` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.name` as `Equivalent`.
ImplementationGuide.definition.resource.descriptiondescriptionis equivalent toImplementationGuide.package.resource.descriptionImplementationGuide.package.resource.descriptionElement `ImplementationGuide.definition.resource.description` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.description` is mapped to FHIR STU3 element `ImplementationGuide.package.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.example[x]example[x]is related toImplementationGuide.package.resource.exampleImplementationGuide.package.resource.exampleElement `ImplementationGuide.definition.resource.example[x]` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.example` as `SourceIsBroaderThanTarget`. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.exampleFor` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types: canonical. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types based on type expansion: value. Examples: * StructureDefinition -> Any * ValueSet -> expansion * OperationDefinition -> Parameters * Questionnaire -> QuestionnaireResponse.
is related toImplementationGuide.package.resource.exampleForImplementationGuide.package.resource.exampleForElement `ImplementationGuide.definition.resource.example[x]` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.example` as `SourceIsBroaderThanTarget`. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.exampleFor` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types: canonical. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types based on type expansion: value. Examples: * StructureDefinition -> Any * ValueSet -> expansion * OperationDefinition -> Parameters * Questionnaire -> QuestionnaireResponse.
ImplementationGuide.manifest.pagepagemaps to wider conceptImplementationGuide.pageImplementationGuide.pageElement `ImplementationGuide.manifest.page` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.page` is mapped to FHIR STU3 element `ImplementationGuide.page` as `SourceIsBroaderThanTarget`.
ImplementationGuide.manifest.page.namenamemaps to wider conceptImplementationGuide.page.sourceImplementationGuide.page.sourceElement `ImplementationGuide.manifest.page.name` is part of an existing definition because parent element `ImplementationGuide.manifest.page` requires a cross-version extension. Element `ImplementationGuide.manifest.page.name` is mapped to FHIR STU3 element `ImplementationGuide.page.source` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.manifest.page.name` do not cover the following types: string. The mappings for `ImplementationGuide.manifest.page.name` do not cover the following types based on type expansion: value. Appending 'rendering' + "/" + this should resolve to the page.
ImplementationGuide.manifest.page.titletitleis equivalent toImplementationGuide.page.titleImplementationGuide.page.titleElement `ImplementationGuide.manifest.page.title` is part of an existing definition because parent element `ImplementationGuide.manifest.page` requires a cross-version extension. Element `ImplementationGuide.manifest.page.title` is mapped to FHIR STU3 element `ImplementationGuide.page.title` as `Equivalent`.
ImplementationGuide.manifest.otherothermaps to wider conceptImplementationGuide.binaryImplementationGuide.binaryElement `ImplementationGuide.manifest.other` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.other` is mapped to FHIR STU3 element `ImplementationGuide.binary` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.manifest.other` do not cover the following types: string. The mappings for `ImplementationGuide.manifest.other` do not cover the following types based on type expansion: value.

Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: Name for this implementation guide (human friendly) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.title (title)maps to wider conceptExtension (R4: Name for this implementation guide (human friendly) (new))Element `ImplementationGuide.title` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.title` has no mapping targets in FHIR STU3. 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.

Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: NPM Package name for IG (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.packageId (packageId)maps to wider conceptExtension (R4: NPM Package name for IG (new))Element `ImplementationGuide.packageId` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.packageId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: SPDX license code for this IG (or not-open-source) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.license (license)maps to wider conceptExtension (R4: SPDX license code for this IG (or not-open-source) (new))Element `ImplementationGuide.license` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.license` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: FHIR Version(s) this Implementation Guide targets additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.fhirVersion (fhirVersion)is equivalent toExtension (R4: FHIR Version(s) this Implementation Guide targets additional types)Element `ImplementationGuide.fhirVersion` is mapped to FHIR STU3 element `ImplementationGuide.fhirVersion` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.fhirVersion` do not cover the following types: code. The mappings for `ImplementationGuide.fhirVersion` do not cover the following types based on type expansion: value. 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.

Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: Type this profile applies toversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.global.type (type)is equivalent toExtension (R4: Type this profile applies to)Element `ImplementationGuide.global.type` is mapped to FHIR STU3 element `ImplementationGuide.global.type` as `SourceIsBroaderThanTarget`. 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 7 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: profile additional typesversion: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.global.profile (profile)is equivalent toExtension (R4: profile additional types)Element `ImplementationGuide.global.profile` is mapped to FHIR STU3 element `ImplementationGuide.global.profile` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.global.profile` do not cover the following types: canonical. The mappings for `ImplementationGuide.global.profile` do not cover the following types based on type expansion: value.

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: Information needed to build the IG (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.definition (definition)maps to wider conceptExtension (R4: Information needed to build the IG (new))Element `ImplementationGuide.definition` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Principally, this consists of information abuot source resource and file locations, and build parameters and templates.
ImplementationGuide.definition.grouping (grouping)is equivalent toExtension.extension:grouping (R4: Grouping used to present related resources in the IG)Element `ImplementationGuide.definition.grouping` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.grouping` is mapped to FHIR STU3 element `ImplementationGuide.package` 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 toExtension.extension:grouping.extension:name (R4: Descriptive name for the package)Element `ImplementationGuide.definition.grouping.name` is part of an existing definition because parent element `ImplementationGuide.definition.grouping` requires a cross-version extension. Element `ImplementationGuide.definition.grouping.name` is mapped to FHIR STU3 element `ImplementationGuide.package.name` as `Equivalent`.
ImplementationGuide.definition.grouping.description (description)is equivalent toExtension.extension:grouping.extension:description (R4: description)Element `ImplementationGuide.definition.grouping.description` is part of an existing definition because parent element `ImplementationGuide.definition.grouping` requires a cross-version extension. Element `ImplementationGuide.definition.grouping.description` is mapped to FHIR STU3 element `ImplementationGuide.package.description` as `Equivalent`.
ImplementationGuide.definition.resource (resource)is equivalent toExtension.extension:resource (R4: resource)Element `ImplementationGuide.definition.resource` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.resource` is mapped to FHIR STU3 element `ImplementationGuide.package.resource` as `Equivalent`.
ImplementationGuide.definition.resource.reference (reference)is equivalent toExtension.extension:resource.extension:reference (R4: reference)Element `ImplementationGuide.definition.resource.reference` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.reference` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.source[x]` as `Equivalent`. The target context `ImplementationGuide.package.resource.source[x]` is a choice-type element and cannot directly hold extensions. The context is moved up to parent element `ImplementationGuide.package.resource`. 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)maps to wider conceptExtension.extension:resource.extension:fhirVersion (R4: Versions this applies to (if different to IG) (new))Element `ImplementationGuide.definition.resource.fhirVersion` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.fhirVersion` has a context of ImplementationGuide.package.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.resource.fhirVersion` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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 toExtension.extension:resource.extension:name (R4: name)Element `ImplementationGuide.definition.resource.name` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.name` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.name` as `Equivalent`.
ImplementationGuide.definition.resource.description (description)is equivalent toExtension.extension:resource.extension:description (R4: description)Element `ImplementationGuide.definition.resource.description` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.description` is mapped to FHIR STU3 element `ImplementationGuide.package.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.example[x] (example[x])maps to wider conceptExtension.extension:resource.extension:example (R4: Is an example/What is this an example of? additional types)Element `ImplementationGuide.definition.resource.example[x]` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.example` as `SourceIsBroaderThanTarget`. Element `ImplementationGuide.definition.resource.example[x]` is mapped to FHIR STU3 element `ImplementationGuide.package.resource.exampleFor` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types: canonical. The mappings for `ImplementationGuide.definition.resource.example[x]` do not cover the following types based on type expansion: value. Examples: * StructureDefinition -> Any * ValueSet -> expansion * OperationDefinition -> Parameters * Questionnaire -> QuestionnaireResponse.
ImplementationGuide.definition.resource.groupingId (groupingId)maps to wider conceptExtension.extension:resource.extension:groupingId (R4: Grouping this is part of (new))Element `ImplementationGuide.definition.resource.groupingId` is part of an existing definition because parent element `ImplementationGuide.definition.resource` requires a cross-version extension. Element `ImplementationGuide.definition.resource.groupingId` has a context of ImplementationGuide.package.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.resource.groupingId` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). This must correspond to a package.id element within this implementation guide.
ImplementationGuide.definition.page (page)maps to wider conceptExtension.extension:page (R4: Page/Section in the Guide (new))Element `ImplementationGuide.definition.page` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.page` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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])maps to wider conceptExtension.extension:page.extension:name (R4: Where to find that page (new))Element `ImplementationGuide.definition.page.name[x]` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.name[x]` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.name[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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)maps to wider conceptExtension.extension:page.extension:title (R4: Short title shown for navigational assistance (new))Element `ImplementationGuide.definition.page.title` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.title` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.page.generation (generation)maps to wider conceptExtension.extension:page.extension:generation (R4: html | markdown | xml | generated (new))Element `ImplementationGuide.definition.page.generation` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.generation` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.generation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.page.page (page)maps to wider conceptExtension.extension:page.extension:page (R4: Nested Pages / Sections (new))Element `ImplementationGuide.definition.page.page` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.page` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.page` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.
ImplementationGuide.definition.parameter (parameter)maps to wider conceptExtension.extension:parameter (R4: Defines how IG is built by tools (new))Element `ImplementationGuide.definition.parameter` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.parameter` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.parameter` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.parameter.code (code)maps to wider conceptExtension.extension:parameter.extension:code (R4: apply | path-resource | path-pages | path-tx-cache | expansion-parameter | rule-broken-links | generate-xml | generate-json | generate-turtle | html-template (new))Element `ImplementationGuide.definition.parameter.code` is part of an existing definition because parent element `ImplementationGuide.definition.parameter` requires a cross-version extension. Element `ImplementationGuide.definition.parameter.code` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.parameter.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.parameter.value (value)maps to wider conceptExtension.extension:parameter.extension:value (R4: Value for named type (new))Element `ImplementationGuide.definition.parameter.value` is part of an existing definition because parent element `ImplementationGuide.definition.parameter` requires a cross-version extension. Element `ImplementationGuide.definition.parameter.value` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.parameter.value` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.template (template)maps to wider conceptExtension.extension:template (R4: A template for building resources (new))Element `ImplementationGuide.definition.template` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.template` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.template` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.template.code (code)maps to wider conceptExtension.extension:template.extension:code (R4: Type of template specified (new))Element `ImplementationGuide.definition.template.code` is part of an existing definition because parent element `ImplementationGuide.definition.template` requires a cross-version extension. Element `ImplementationGuide.definition.template.code` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.template.code` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.template.source (source)maps to wider conceptExtension.extension:template.extension:source (R4: The source location for the template (new))Element `ImplementationGuide.definition.template.source` is part of an existing definition because parent element `ImplementationGuide.definition.template` requires a cross-version extension. Element `ImplementationGuide.definition.template.source` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.template.source` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.template.scope (scope)maps to wider conceptExtension.extension:template.extension:scope (R4: The scope in which the template applies (new))Element `ImplementationGuide.definition.template.scope` is part of an existing definition because parent element `ImplementationGuide.definition.template` requires a cross-version extension. Element `ImplementationGuide.definition.template.scope` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.template.scope` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: Page/Section in the Guide (new)version: 0.1.0)

Source Concept DetailsRelationshipTarget Concept DetailsComment
Codes from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1Codes from R4: Page/Section in the Guide (new)
ImplementationGuide.definition.pagepagemaps to wider conceptExtensionElement `ImplementationGuide.definition.page` is part of an existing definition because parent element `ImplementationGuide.definition` requires a cross-version extension. Element `ImplementationGuide.definition.page` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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]maps to wider conceptExtension.extension:nameElement `ImplementationGuide.definition.page.name[x]` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.name[x]` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.name[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.titletitlemaps to wider conceptExtension.extension:titleElement `ImplementationGuide.definition.page.title` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.title` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.title` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.page.generationgenerationmaps to wider conceptExtension.extension:generationElement `ImplementationGuide.definition.page.generation` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.generation` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.generation` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.definition.page.pagepagemaps to wider conceptExtension.extension:page.extension:pageElement `ImplementationGuide.definition.page.page` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.page` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.page` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.
maps to wider conceptExtension.extension:pageElement `ImplementationGuide.definition.page.page` is part of an existing definition because parent element `ImplementationGuide.definition.page` requires a cross-version extension. Element `ImplementationGuide.definition.page.page` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.definition.page.page` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|4.0.1 to R4: Information about an assembled IG (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
ImplementationGuide.manifest (manifest)maps to wider conceptExtension (R4: Information about an assembled IG (new))Element `ImplementationGuide.manifest` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.manifest.rendering (rendering)maps to wider conceptExtension.extension:rendering (R4: Location of rendered implementation guide (new))Element `ImplementationGuide.manifest.rendering` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.rendering` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.rendering` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.manifest.resource (resource)maps to wider conceptExtension.extension:resource (R4: Resource in the implementation guide (new))Element `ImplementationGuide.manifest.resource` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.resource` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.resource` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.manifest.resource.reference (reference)maps to wider conceptExtension.extension:resource.extension:reference (R4: Location of the resource (new))Element `ImplementationGuide.manifest.resource.reference` is part of an existing definition because parent element `ImplementationGuide.manifest.resource` requires a cross-version extension. Element `ImplementationGuide.manifest.resource.reference` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.resource.reference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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.example[x] (example[x])maps to wider conceptExtension.extension:resource.extension:example (R4: Is an example/What is this an example of? (new))Element `ImplementationGuide.manifest.resource.example[x]` is part of an existing definition because parent element `ImplementationGuide.manifest.resource` requires a cross-version extension. Element `ImplementationGuide.manifest.resource.example[x]` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.resource.example[x]` has no mapping targets in FHIR STU3. 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.
ImplementationGuide.manifest.resource.relativePath (relativePath)maps to wider conceptExtension.extension:resource.extension:relativePath (R4: Relative path for page in IG (new))Element `ImplementationGuide.manifest.resource.relativePath` is part of an existing definition because parent element `ImplementationGuide.manifest.resource` requires a cross-version extension. Element `ImplementationGuide.manifest.resource.relativePath` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.resource.relativePath` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Appending 'rendering' + "/" + this should resolve to the resource page.
ImplementationGuide.manifest.page (page)maps to wider conceptExtension.extension:page (R4: HTML page within the parent IG)Element `ImplementationGuide.manifest.page` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.page` is mapped to FHIR STU3 element `ImplementationGuide.page` as `SourceIsBroaderThanTarget`.
ImplementationGuide.manifest.page.name (name)maps to wider conceptExtension.extension:page.extension:name (R4: HTML page name additional types)Element `ImplementationGuide.manifest.page.name` is part of an existing definition because parent element `ImplementationGuide.manifest.page` requires a cross-version extension. Element `ImplementationGuide.manifest.page.name` is mapped to FHIR STU3 element `ImplementationGuide.page.source` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.manifest.page.name` do not cover the following types: string. The mappings for `ImplementationGuide.manifest.page.name` do not cover the following types based on type expansion: value. Appending 'rendering' + "/" + this should resolve to the page.
ImplementationGuide.manifest.page.title (title)is equivalent toExtension.extension:page.extension:title (R4: Title of the page, for references)Element `ImplementationGuide.manifest.page.title` is part of an existing definition because parent element `ImplementationGuide.manifest.page` requires a cross-version extension. Element `ImplementationGuide.manifest.page.title` is mapped to FHIR STU3 element `ImplementationGuide.page.title` as `Equivalent`.
ImplementationGuide.manifest.page.anchor (anchor)maps to wider conceptExtension.extension:page.extension:anchor (R4: Anchor available on the page (new))Element `ImplementationGuide.manifest.page.anchor` is part of an existing definition because parent element `ImplementationGuide.manifest.page` requires a cross-version extension. Element `ImplementationGuide.manifest.page.anchor` has a context of ImplementationGuide.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.page.anchor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Appending 'rendering' + "/" + page.name + "#" + page.anchor should resolve to the anchor.
ImplementationGuide.manifest.image (image)maps to wider conceptExtension.extension:image (R4: Image within the IG (new))Element `ImplementationGuide.manifest.image` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.image` has a context of ImplementationGuide based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.manifest.image` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
ImplementationGuide.manifest.other (other)maps to wider conceptExtension.extension:other (R4: Additional linkable file in IG additional types)Element `ImplementationGuide.manifest.other` is part of an existing definition because parent element `ImplementationGuide.manifest` requires a cross-version extension. Element `ImplementationGuide.manifest.other` is mapped to FHIR STU3 element `ImplementationGuide.binary` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.manifest.other` do not cover the following types: string. The mappings for `ImplementationGuide.manifest.other` do not cover the following types based on type expansion: value.