Generated Narrative: ConceptMap R3-ImplementationGuide-element-map-to-R5 Mapping from http://hl7.org/fhir/3.0 to http://hl7.org/fhir/5.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to ImplementationGuideversion: 5.0.0) Source Code Relationship Target Code Comment ImplementationGuide.meta (meta) is broader than ImplementationGuide.meta Element `ImplementationGuide.meta` is mapped to FHIR R5 element `ImplementationGuide.meta` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.meta` do not cover the following types: Meta. The mappings for `ImplementationGuide.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. ImplementationGuide.implicitRules (implicitRules) is equivalent to ImplementationGuide.implicitRules Element `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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. ImplementationGuide.language (language) is equivalent to ImplementationGuide.language Element `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 broader than ImplementationGuide.text Element `ImplementationGuide.text` is mapped to FHIR R5 element `ImplementationGuide.text` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.text` do not cover the following types: Narrative. The mappings for `ImplementationGuide.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. ImplementationGuide.contained (contained) is equivalent to ImplementationGuide.contained Element `ImplementationGuide.contained` is mapped to FHIR R5 element `ImplementationGuide.contained` as `SourceIsBroaderThanTarget`. 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. ImplementationGuide.url (url) is equivalent to ImplementationGuide.url Element `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. ImplementationGuide.version (version) is equivalent to ImplementationGuide.version Element `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 refrence to a particular business version of the implementation guide with the format [url]|[version]. ImplementationGuide.name (name) is equivalent to ImplementationGuide.name Element `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 alpha-numeric type name to ensure that it is computable friendly. ImplementationGuide.status (status) is equivalent to ImplementationGuide.status Element `ImplementationGuide.status` is mapped to FHIR R5 element `ImplementationGuide.status` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired implementation guide without due consideration. ImplementationGuide.experimental (experimental) is equivalent to ImplementationGuide.experimental Element `ImplementationGuide.experimental` is mapped to FHIR R5 element `ImplementationGuide.experimental` as `Equivalent`. Allows filtering of implementation guide that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental implementation guide in production. ImplementationGuide.date (date) is equivalent to ImplementationGuide.date Element `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 to ImplementationGuide.publisher Element `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 broader than ImplementationGuide.contact Element `ImplementationGuide.contact` is mapped to FHIR R5 element `ImplementationGuide.contact` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.contact` do not cover the following types: ContactDetail. The mappings for `ImplementationGuide.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. ImplementationGuide.description (description) is equivalent to ImplementationGuide.description Element `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 profile is presumed to be the predominant language in the place the profile was created). ImplementationGuide.useContext (useContext) is broader than ImplementationGuide.useContext Element `ImplementationGuide.useContext` is mapped to FHIR R5 element `ImplementationGuide.useContext` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.useContext` do not cover the following types: UsageContext. The mappings for `ImplementationGuide.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. ImplementationGuide.jurisdiction (jurisdiction) is equivalent to ImplementationGuide.jurisdiction Element `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 to ImplementationGuide.copyright Element `ImplementationGuide.copyright` is mapped to FHIR R5 element `ImplementationGuide.copyright` as `Equivalent`. ImplementationGuide.fhirVersion (fhirVersion) is equivalent to ImplementationGuide.fhirVersion Element `ImplementationGuide.fhirVersion` is mapped to FHIR R5 element `ImplementationGuide.fhirVersion` as `SourceIsNarrowerThanTarget`. An Implementation Guide should specify the target it applies to, as ImplementationGuides are rarely valid across multiple versions of FHIR. ImplementationGuide.dependency (dependency) is broader than ImplementationGuide.dependsOn Element `ImplementationGuide.dependency` is mapped to FHIR R5 element `ImplementationGuide.dependsOn` as `Equivalent`. ImplementationGuide.dependency.uri (uri) is equivalent to ImplementationGuide.dependsOn.uri Element `ImplementationGuide.dependency.uri` is mapped to FHIR R5 element `ImplementationGuide.dependsOn.uri` as `Equivalent`. When a guide is published, and the type is 'include', this will be a relative reference within the guide. ImplementationGuide.package (package) is broader than ImplementationGuide.definition.grouping Element `ImplementationGuide.package` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping` as `Equivalent`. ImplementationGuide.package.name (name) is equivalent to ImplementationGuide.definition.grouping.name Element `ImplementationGuide.package.name` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.name` as `Equivalent`. ImplementationGuide.package.description (description) is equivalent to ImplementationGuide.definition.grouping.description Element `ImplementationGuide.package.description` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.description` as `Equivalent`. ImplementationGuide.package.resource (resource) is broader than ImplementationGuide.definition.resource Element `ImplementationGuide.package.resource` is mapped to FHIR R5 element `ImplementationGuide.definition.resource` as `Equivalent`. ImplementationGuide.package.resource.name (name) is equivalent to ImplementationGuide.definition.resource.name Element `ImplementationGuide.package.resource.name` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.name` as `Equivalent`. ImplementationGuide.package.resource.description (description) is equivalent to ImplementationGuide.definition.resource.description Element `ImplementationGuide.package.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.package.resource.source[x] (source[x]) is broader than ImplementationGuide.definition.resource.reference Element `ImplementationGuide.package.resource.source[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.reference` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types: uri. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR STU3 element `ImplementationGuide.package.resource.source[x]` with unmapped reference targets: 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.global (global) is broader than ImplementationGuide.global Element `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 than ImplementationGuide.global.type 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. ImplementationGuide.global.profile (profile) is broader than ImplementationGuide.global.profile Element `ImplementationGuide.global.profile` is mapped to FHIR R5 element `ImplementationGuide.global.profile` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.global.profile` do not cover the following types: Reference. The mappings for `ImplementationGuide.global.profile` do not cover the following types based on type expansion: display, identifier, reference. ImplementationGuide.binary (binary) is narrower than ImplementationGuide.manifest.other Element `ImplementationGuide.binary` is mapped to FHIR R5 element `ImplementationGuide.manifest.other` as `SourceIsNarrowerThanTarget`. This is principally included for the FHIR publishing tool, but may be useful when extracting and reusing content from the implementation guide. ImplementationGuide.page (page) is related to ImplementationGuide.manifest.page Element `ImplementationGuide.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `SourceIsNarrowerThanTarget`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html. ImplementationGuide.page.source (source) is narrower than ImplementationGuide.manifest.page.name Element `ImplementationGuide.page.source` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `SourceIsNarrowerThanTarget`. The publishing tool will autogenerate source for list (source = n/a), and inject included implementations for include (source = uri of guide to include). ImplementationGuide.page.title (title) is equivalent to ImplementationGuide.manifest.page.title Element `ImplementationGuide.page.title` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.title` as `Equivalent`. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: meta additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.meta (meta) is equivalent to Extension (STU3: meta additional types) Element `ImplementationGuide.meta` is mapped to FHIR R5 element `ImplementationGuide.meta` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.meta` do not cover the following types: Meta. The mappings for `ImplementationGuide.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: text additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.text (text) is equivalent to Extension (STU3: text additional types) Element `ImplementationGuide.text` is mapped to FHIR R5 element `ImplementationGuide.text` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.text` do not cover the following types: Narrative. The mappings for `ImplementationGuide.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: contact additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.contact (contact) is equivalent to Extension (STU3: contact additional types) Element `ImplementationGuide.contact` is mapped to FHIR R5 element `ImplementationGuide.contact` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.contact` do not cover the following types: ContactDetail. The mappings for `ImplementationGuide.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Context the content is intended to support additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.useContext (useContext) is equivalent to Extension (STU3: Context the content is intended to support additional types) Element `ImplementationGuide.useContext` is mapped to FHIR R5 element `ImplementationGuide.useContext` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.useContext` do not cover the following types: UsageContext. The mappings for `ImplementationGuide.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: reference | inclusion (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.dependency.type (type) is equivalent to Extension (STU3: reference | inclusion (new)) Element `ImplementationGuide.dependency.type` has a context of ImplementationGuide.dependsOn based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.dependency.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). For information about processing included guides, see [Including Guides]{implementationguide.html#include}. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: If not an example, has its normal meaning (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.package.resource.example (example) is broader than Extension (STU3: If not an example, has its normal meaning (new)) Element `ImplementationGuide.package.resource.example` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.example` 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. Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Short code to identify the resource (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.package.resource.acronym (acronym) is equivalent to Extension (STU3: Short code to identify the resource (new)) Element `ImplementationGuide.package.resource.acronym` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.acronym` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is used when generating schematrons from profiles, for example, but has other uses. Publishing tooling may autogenerate this value, but a human assigned value is more useful. This value must be unique within an implementation guide (across included guides as well). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: source additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.package.resource.source[x] (source[x]) is broader than Extension (STU3: source additional types) Element `ImplementationGuide.package.resource.source[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.reference` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types: uri. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR STU3 element `ImplementationGuide.package.resource.source[x]` with unmapped reference targets: 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. Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to Alternate Referenceversion: 5.2.0) Source Code Relationship Target Code Comment ImplementationGuide.package.resource.source[x] (source[x]) is broader than Extension (Alternative reference (target type is wrong)) Element `ImplementationGuide.package.resource.source[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.reference` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types: uri. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR STU3 element `ImplementationGuide.package.resource.source[x]` with unmapped reference targets: 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. Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Resource this is an example of (if applicable) (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.package.resource.exampleFor (exampleFor) is broader than Extension (STU3: Resource this is an example of (if applicable) (new)) Element `ImplementationGuide.package.resource.exampleFor` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.exampleFor` 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 12 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Type this profiles applies to additional codesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.global.type (type) is equivalent to Extension (STU3: Type this profiles applies to 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 13 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: profile additional typesversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.global.profile (profile) is equivalent to Extension (STU3: profile additional types) Element `ImplementationGuide.global.profile` is mapped to FHIR R5 element `ImplementationGuide.global.profile` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.global.profile` do not cover the following types: Reference. The mappings for `ImplementationGuide.global.profile` do not cover the following types based on type expansion: display, identifier, reference. Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Page/Section in the Guideversion: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.page (page) is broader than Extension (STU3: Page/Section in the Guide) Element `ImplementationGuide.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `SourceIsNarrowerThanTarget`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html. ImplementationGuide.page.source (source) is broader than Extension.extension:source (STU3: Where to find that page) Element `ImplementationGuide.page.source` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `SourceIsNarrowerThanTarget`. The publishing tool will autogenerate source for list (source = n/a), and inject included implementations for include (source = uri of guide to include). ImplementationGuide.page.title (title) is equivalent to Extension.extension:title (STU3: Short title shown for navigational assistance) Element `ImplementationGuide.page.title` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.title` as `Equivalent`. ImplementationGuide.page.kind (kind) is equivalent to Extension.extension:kind (STU3: page | example | list | include | directory | dictionary | toc | resource (new)) Element `ImplementationGuide.page.kind` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.kind` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). ImplementationGuide.page.type (type) is equivalent to Extension.extension:type (STU3: Kind of resource to include in the list (new)) Element `ImplementationGuide.page.type` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). ImplementationGuide.page.package (package) is equivalent to Extension.extension:package (STU3: Name of package to include (new)) Element `ImplementationGuide.page.package` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.package` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). ImplementationGuide.page.format (format) is equivalent to Extension.extension:format (STU3: Format of the page (e.g. html, markdown, etc.) (new)) Element `ImplementationGuide.page.format` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx. ImplementationGuide.page.page (page) is equivalent to Extension.extension:page (STU3: Nested Pages / Sections (new)) Element `ImplementationGuide.page.page` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.page` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure. Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: page | example | list | include | directory | dictionary | toc | resource (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.page.kind (kind) is equivalent to Extension (STU3: page | example | list | include | directory | dictionary | toc | resource (new)) Element `ImplementationGuide.page.kind` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.kind` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Kind of resource to include in the list (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.page.type (type) is equivalent to Extension (STU3: Kind of resource to include in the list (new)) Element `ImplementationGuide.page.type` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Name of package to include (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.page.package (package) is equivalent to Extension (STU3: Name of package to include (new)) Element `ImplementationGuide.page.package` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.package` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/ImplementationGuide|3.0.2 to STU3: Format of the page (e.g. html, markdown, etc.) (new)version: 0.1.0) Source Code Relationship Target Code Comment ImplementationGuide.page.format (format) is equivalent to Extension (STU3: Format of the page (e.g. html, markdown, etc.) (new)) Element `ImplementationGuide.page.format` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx.
Cross-version mapping for FHIR STU3 ImplementationGuide to FHIR R5 ImplementationGuide
This ConceptMap represents cross-version mappings for elements from a FHIR STU3 ImplementationGuide to FHIR R5.
Element `ImplementationGuide.meta` is mapped to FHIR R5 element `ImplementationGuide.meta` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.meta` do not cover the following types: Meta. The mappings for `ImplementationGuide.meta` do not cover the following types based on type expansion: lastUpdated, profile, security, tag, versionId.
Element `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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation.
Element `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).
Element `ImplementationGuide.text` is mapped to FHIR R5 element `ImplementationGuide.text` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.text` do not cover the following types: Narrative. The mappings for `ImplementationGuide.text` do not cover the following types based on type expansion: div, status. Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later.
Element `ImplementationGuide.contained` is mapped to FHIR R5 element `ImplementationGuide.contained` as `SourceIsBroaderThanTarget`. This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.
Element `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.
Element `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 refrence to a particular business version of the implementation guide with the format [url]|[version].
Element `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 alpha-numeric type name to ensure that it is computable friendly.
Element `ImplementationGuide.status` is mapped to FHIR R5 element `ImplementationGuide.status` as `Equivalent`. Allows filtering of implementation guides that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use a retired implementation guide without due consideration.
Element `ImplementationGuide.experimental` is mapped to FHIR R5 element `ImplementationGuide.experimental` as `Equivalent`. Allows filtering of implementation guide that are appropriate for use vs. not. This is labeled as "Is Modifier" because applications should not use an experimental implementation guide in production.
Element `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.
Element `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.
Element `ImplementationGuide.contact` is mapped to FHIR R5 element `ImplementationGuide.contact` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.contact` do not cover the following types: ContactDetail. The mappings for `ImplementationGuide.contact` do not cover the following types based on type expansion: name, telecom. May be a web site, an email address, a telephone number, etc.
Element `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 profile is presumed to be the predominant language in the place the profile was created).
Element `ImplementationGuide.useContext` is mapped to FHIR R5 element `ImplementationGuide.useContext` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.useContext` do not cover the following types: UsageContext. The mappings for `ImplementationGuide.useContext` do not cover the following types based on type expansion: code, value[x]. When multiple useContexts are specified, there is no expectation whether all or any of the contexts apply.
Element `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.
Element `ImplementationGuide.copyright` is mapped to FHIR R5 element `ImplementationGuide.copyright` as `Equivalent`.
Element `ImplementationGuide.fhirVersion` is mapped to FHIR R5 element `ImplementationGuide.fhirVersion` as `SourceIsNarrowerThanTarget`. An Implementation Guide should specify the target it applies to, as ImplementationGuides are rarely valid across multiple versions of FHIR.
Element `ImplementationGuide.dependency` is mapped to FHIR R5 element `ImplementationGuide.dependsOn` as `Equivalent`.
Element `ImplementationGuide.dependency.uri` is mapped to FHIR R5 element `ImplementationGuide.dependsOn.uri` as `Equivalent`. When a guide is published, and the type is 'include', this will be a relative reference within the guide.
Element `ImplementationGuide.package` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping` as `Equivalent`.
Element `ImplementationGuide.package.name` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.name` as `Equivalent`.
Element `ImplementationGuide.package.description` is mapped to FHIR R5 element `ImplementationGuide.definition.grouping.description` as `Equivalent`.
Element `ImplementationGuide.package.resource` is mapped to FHIR R5 element `ImplementationGuide.definition.resource` as `Equivalent`.
Element `ImplementationGuide.package.resource.name` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.name` as `Equivalent`.
Element `ImplementationGuide.package.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).
Element `ImplementationGuide.package.resource.source[x]` is mapped to FHIR R5 element `ImplementationGuide.definition.resource.reference` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types: uri. The mappings for `ImplementationGuide.package.resource.source[x]` do not cover the following types based on type expansion: display, identifier, reference, value. The standard extension `alternate-reference` has been mapped as PART of the representation of FHIR STU3 element `ImplementationGuide.package.resource.source[x]` with unmapped reference targets: 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.
Element `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.
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.
Element `ImplementationGuide.global.profile` is mapped to FHIR R5 element `ImplementationGuide.global.profile` as `SourceIsBroaderThanTarget`. The mappings for `ImplementationGuide.global.profile` do not cover the following types: Reference. The mappings for `ImplementationGuide.global.profile` do not cover the following types based on type expansion: display, identifier, reference.
Element `ImplementationGuide.binary` is mapped to FHIR R5 element `ImplementationGuide.manifest.other` as `SourceIsNarrowerThanTarget`. This is principally included for the FHIR publishing tool, but may be useful when extracting and reusing content from the implementation guide.
Element `ImplementationGuide.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `SourceIsNarrowerThanTarget`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html.
Element `ImplementationGuide.page.source` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `SourceIsNarrowerThanTarget`. The publishing tool will autogenerate source for list (source = n/a), and inject included implementations for include (source = uri of guide to include).
Element `ImplementationGuide.page.title` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.title` as `Equivalent`.
Element `ImplementationGuide.dependency.type` has a context of ImplementationGuide.dependsOn based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.dependency.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). For information about processing included guides, see [Including Guides]{implementationguide.html#include}.
Element `ImplementationGuide.package.resource.example` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.example` 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.
Element `ImplementationGuide.package.resource.acronym` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.acronym` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is used when generating schematrons from profiles, for example, but has other uses. Publishing tooling may autogenerate this value, but a human assigned value is more useful. This value must be unique within an implementation guide (across included guides as well).
Element `ImplementationGuide.package.resource.exampleFor` has a context of ImplementationGuide.definition.resource based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.package.resource.exampleFor` 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.
Element `ImplementationGuide.page.kind` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.kind` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `ImplementationGuide.page.type` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `ImplementationGuide.page.package` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.package` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Element `ImplementationGuide.page.format` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx.
Element `ImplementationGuide.page.page` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.page` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.