Generated Narrative: ConceptMap R5-EvidenceReport-element-map-to-R4 Mapping from http://hl7.org/fhir/5.0 to http://hl7.org/fhir/4.0 Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to Basicversion: 4.0.1) Source Code Relationship Target Code Comment EvidenceReport.meta (meta) is equivalent to Basic.meta Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `EvidenceReport.meta` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.implicitRules (implicitRules) is equivalent to Basic.implicitRules Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `EvidenceReport.implicitRules` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc. EvidenceReport.language (language) is equivalent to Basic.language Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `EvidenceReport.language` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). EvidenceReport.text (text) is equivalent to Basic.text Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `EvidenceReport.text` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Contained resources do not have a 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. EvidenceReport.contained (contained) is equivalent to Basic.contained Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `EvidenceReport.contained` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. EvidenceReport.identifier (identifier) is equivalent to Basic.identifier Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `EvidenceReport.identifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element will contain unique identifiers that support de-duplication of EvidenceReports. This identifier can be valid for only one EvidenceReport resource. Group 2 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Canonical identifier for this EvidenceReport, represented as a globally unique URI (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.url (url) maps to wider concept Extension (R5: Canonical identifier for this EvidenceReport, represented as a globally unique URI (new)) Element `EvidenceReport.url` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version. Group 3 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: draft | active | retired | unknown (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.status (status) maps to wider concept Extension (R5: draft | active | retired | unknown (new)) Element `EvidenceReport.status` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of summaries that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: The context that the content is intended to support (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.useContext (useContext) maps to wider concept Extension (R5: The context that the content is intended to support (new)) Element `EvidenceReport.useContext` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply. Group 5 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Identifiers for articles that may relate to more than one evidence report (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.relatedIdentifier (relatedIdentifier) maps to wider concept Extension (R5: Identifiers for articles that may relate to more than one evidence report (new)) Element `EvidenceReport.relatedIdentifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatedIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May include trial registry identifiers, e.g. NCT04372602 from clinicaltrials.gov. This identifier can be valid for multiple EvidenceReport resources. Group 6 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Citation for this report (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.citeAs[x] (citeAs[x]) maps to wider concept Extension (R5: Citation for this report (new)) Element `EvidenceReport.citeAs[x]` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.citeAs[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). used for reports for which external citation is expected, such as use in support of scholarly publications. Group 7 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Kind of report (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.type (type) maps to wider concept Extension (R5: Kind of report (new)) Element `EvidenceReport.type` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Used for footnotes and annotations (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.note (note) maps to wider concept Extension (R5: Used for footnotes and annotations (new)) Element `EvidenceReport.note` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Link, description or reference to artifact associated with the report (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.relatedArtifact (relatedArtifact) maps to wider concept Extension (R5: Link, description or reference to artifact associated with the report (new)) Element `EvidenceReport.relatedArtifact` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Focus of the report (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.subject (subject) maps to wider concept Extension (R5: Focus of the report (new)) Element `EvidenceReport.subject` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). While the source element matches Basic element path `` (``), the definitions are not compatible (source: `BackboneElement`:1..1 -> basic: `Reference(http://hl7.org/fhir/StructureDefinition/Resource)`:0..1). May be used as an expression for search queries and search results EvidenceReport.subject.characteristic (characteristic) maps to wider concept Extension.extension:characteristic (R5: Characteristic (new)) Element `EvidenceReport.subject.characteristic` is part of an existing definition because parent element `EvidenceReport.subject` requires a cross-version extension. Element `EvidenceReport.subject.characteristic` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.subject.characteristic.code (code) maps to wider concept Extension.extension:characteristic.extension:code (R5: Characteristic code (new)) Element `EvidenceReport.subject.characteristic.code` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.code` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Example 1 is a Citation. Example 2 is a type of outcome. Example 3 is a specific outcome. EvidenceReport.subject.characteristic.value[x] (value[x]) maps to wider concept Extension.extension:characteristic.extension:value (R5: Characteristic value (new)) Element `EvidenceReport.subject.characteristic.value[x]` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.value[x]` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Example 1 is Citation #37. Example 2 is selecting clinical outcomes. Example 3 is 1-year mortality. EvidenceReport.subject.characteristic.exclude (exclude) maps to wider concept Extension.extension:characteristic.extension:exclude (R5: Is used to express not the characteristic (new)) Element `EvidenceReport.subject.characteristic.exclude` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.exclude` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.exclude` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.subject.characteristic.period (period) maps to wider concept Extension.extension:characteristic.extension:period (R5: Timeframe for the characteristic (new)) Element `EvidenceReport.subject.characteristic.period` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.period` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.subject.note (note) maps to wider concept Extension.extension:note (R5: Footnotes and/or explanatory notes (new)) Element `EvidenceReport.subject.note` is part of an existing definition because parent element `EvidenceReport.subject` requires a cross-version extension. Element `EvidenceReport.subject.note` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Name of the publisher/steward (organization or individual) (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.publisher (publisher) maps to wider concept Extension (R5: Name of the publisher/steward (organization or individual) (new)) Element `EvidenceReport.publisher` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the evidence report is the organization or individual primarily responsible for the maintenance and upkeep of the evidence report. 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 evidence report. This item SHOULD be populated unless the information is available from context. Group 12 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Contact details for the publisher (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.contact (contact) maps to wider concept Extension (R5: Contact details for the publisher (new)) Element `EvidenceReport.contact` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Who authored the content (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.author (author) maps to wider concept Extension (R5: Who authored the content (new)) Element `EvidenceReport.author` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.author` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). While the source element matches Basic element path `` (``), the definitions are not compatible (source: `ContactDetail`:0..* -> basic: `Reference(http://hl7.org/fhir/StructureDefinition/Practitioner,http://hl7.org/fhir/StructureDefinition/PractitionerRole,http://hl7.org/fhir/StructureDefinition/Patient,http://hl7.org/fhir/StructureDefinition/RelatedPerson,http://hl7.org/fhir/StructureDefinition/Organization)`:0..1). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Who edited the content (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.editor (editor) maps to wider concept Extension (R5: Who edited the content (new)) Element `EvidenceReport.editor` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.editor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Who reviewed the content (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.reviewer (reviewer) maps to wider concept Extension (R5: Who reviewed the content (new)) Element `EvidenceReport.reviewer` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.reviewer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Who endorsed the content (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.endorser (endorser) maps to wider concept Extension (R5: Who endorsed the content (new)) Element `EvidenceReport.endorser` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.endorser` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization). Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Relationships to other compositions/documents (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.relatesTo (relatesTo) maps to wider concept Extension (R5: Relationships to other compositions/documents (new)) Element `EvidenceReport.relatesTo` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A document is a version specific composition. EvidenceReport.relatesTo.code (code) maps to wider concept Extension.extension:code (R5: replaces | amends | appends | transforms | replacedWith | amendedWith | appendedWith | transformedWith (new)) Element `EvidenceReport.relatesTo.code` is part of an existing definition because parent element `EvidenceReport.relatesTo` requires a cross-version extension. Element `EvidenceReport.relatesTo.code` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If this document appends another document, then the document cannot be fully understood without also accessing the referenced document. EvidenceReport.relatesTo.target (target) maps to wider concept Extension.extension:target (R5: Target of the relationship (new)) Element `EvidenceReport.relatesTo.target` is part of an existing definition because parent element `EvidenceReport.relatesTo` requires a cross-version extension. Element `EvidenceReport.relatesTo.target` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.relatesTo.target.url (url) maps to wider concept Extension.extension:target.extension:url (R5: Target of the relationship URL (new)) Element `EvidenceReport.relatesTo.target.url` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.url` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.relatesTo.target.identifier (identifier) maps to wider concept Extension.extension:target.extension:identifier (R5: Target of the relationship Identifier (new)) Element `EvidenceReport.relatesTo.target.identifier` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.identifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.relatesTo.target.display (display) maps to wider concept Extension.extension:target.extension:display (R5: Target of the relationship Display (new)) Element `EvidenceReport.relatesTo.target.display` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.display` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.relatesTo.target.resource (resource) maps to wider concept Extension.extension:target.extension:resource (R5: Target of the relationship Resource reference (new)) Element `EvidenceReport.relatesTo.target.resource` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.resource` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|5.0.0 to R5: Composition is broken into sections (new)version: 0.1.0) Source Code Relationship Target Code Comment EvidenceReport.section (section) maps to wider concept Extension (R5: Composition is broken into sections (new)) Element `EvidenceReport.section` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.section.title (title) maps to wider concept Extension.extension:title (R5: Label for section (e.g. for ToC) (new)) Element `EvidenceReport.section.title` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.title` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section. EvidenceReport.section.focus (focus) maps to wider concept Extension.extension:focus (R5: Classification of section (recommended) (new)) Element `EvidenceReport.section.focus` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.focus` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code. EvidenceReport.section.focusReference (focusReference) maps to wider concept Extension.extension:focusReference (R5: Classification of section by Resource (new)) Element `EvidenceReport.section.focusReference` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.focusReference` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.focusReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.section.author (author) maps to wider concept Extension.extension:author (R5: Who and/or what authored the section (new)) Element `EvidenceReport.section.author` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.author` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.author` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.section.text (text) maps to wider concept Extension.extension:text (R5: Text summary of the section, for human interpretation (new)) Element `EvidenceReport.section.text` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.text` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Document profiles may define what content should be represented in the narrative. EvidenceReport.section.mode (mode) maps to wider concept Extension.extension:mode (R5: working | snapshot | changes (new)) Element `EvidenceReport.section.mode` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.mode` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is labeled as a modifier because a change list must not be misunderstood as a complete list. EvidenceReport.section.orderedBy (orderedBy) maps to wider concept Extension.extension:orderedBy (R5: Order of section entries (new)) Element `EvidenceReport.section.orderedBy` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.orderedBy` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.orderedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order. EvidenceReport.section.entryClassifier (entryClassifier) maps to wider concept Extension.extension:entryClassifier (R5: Extensible classifiers as content (new)) Element `EvidenceReport.section.entryClassifier` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryClassifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryClassifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.section.entryReference (entryReference) maps to wider concept Extension.extension:entryReference (R5: Reference to resources as content (new)) Element `EvidenceReport.section.entryReference` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryReference` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If there are no entries in the list, an emptyReason SHOULD be provided. EvidenceReport.section.entryQuantity (entryQuantity) maps to wider concept Extension.extension:entryQuantity (R5: Quantity as content (new)) Element `EvidenceReport.section.entryQuantity` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryQuantity` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryQuantity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). EvidenceReport.section.emptyReason (emptyReason) maps to wider concept Extension.extension:emptyReason (R5: Why the section is empty (new)) Element `EvidenceReport.section.emptyReason` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.emptyReason` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.emptyReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases. EvidenceReport.section.section (section) maps to wider concept Extension.extension:section (R5: Nested Section (new)) Element `EvidenceReport.section.section` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.section` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.section` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Nested sections are primarily used to help human readers navigate to particular portions of the document.
Cross-version mapping for FHIR R5 EvidenceReport to FHIR R4 Basic
This ConceptMap represents cross-version mappings for elements from a FHIR R5 EvidenceReport to FHIR R4.
Element matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `EvidenceReport.meta` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.meta` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `EvidenceReport.implicitRules` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.implicitRules` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
Element matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `EvidenceReport.language` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.language` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Element matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `EvidenceReport.text` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
Element matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `EvidenceReport.contained` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.contained` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Element matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `EvidenceReport.identifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element will contain unique identifiers that support de-duplication of EvidenceReports. This identifier can be valid for only one EvidenceReport resource.
Element `EvidenceReport.url` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same URL if they have a distinct version.
Element `EvidenceReport.status` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.status` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Allows filtering of summaries that are appropriate for use versus not. See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `EvidenceReport.useContext` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.useContext` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). When multiple useContexts are specified, there is no expectation that all or any of the contexts apply.
Element `EvidenceReport.relatedIdentifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatedIdentifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). May include trial registry identifiers, e.g. NCT04372602 from clinicaltrials.gov. This identifier can be valid for multiple EvidenceReport resources.
Element `EvidenceReport.citeAs[x]` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.citeAs[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). used for reports for which external citation is expected, such as use in support of scholarly publications.
Element `EvidenceReport.type` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.type` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.note` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.relatedArtifact` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatedArtifact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.subject` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). While the source element matches Basic element path `` (``), the definitions are not compatible (source: `BackboneElement`:1..1 -> basic: `Reference(http://hl7.org/fhir/StructureDefinition/Resource)`:0..1). May be used as an expression for search queries and search results
Element `EvidenceReport.subject.characteristic` is part of an existing definition because parent element `EvidenceReport.subject` requires a cross-version extension. Element `EvidenceReport.subject.characteristic` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.subject.characteristic.code` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.code` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Example 1 is a Citation. Example 2 is a type of outcome. Example 3 is a specific outcome.
Element `EvidenceReport.subject.characteristic.value[x]` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.value[x]` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.value[x]` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Example 1 is Citation #37. Example 2 is selecting clinical outcomes. Example 3 is 1-year mortality.
Element `EvidenceReport.subject.characteristic.exclude` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.exclude` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.exclude` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.subject.characteristic.period` is part of an existing definition because parent element `EvidenceReport.subject.characteristic` requires a cross-version extension. Element `EvidenceReport.subject.characteristic.period` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.period` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.subject.note` is part of an existing definition because parent element `EvidenceReport.subject` requires a cross-version extension. Element `EvidenceReport.subject.note` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.subject.note` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.publisher` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.publisher` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Usually an organization but may be an individual. The publisher (or steward) of the evidence report is the organization or individual primarily responsible for the maintenance and upkeep of the evidence report. 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 evidence report. This item SHOULD be populated unless the information is available from context.
Element `EvidenceReport.contact` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.contact` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `EvidenceReport.author` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.author` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). While the source element matches Basic element path `` (``), the definitions are not compatible (source: `ContactDetail`:0..* -> basic: `Reference(http://hl7.org/fhir/StructureDefinition/Practitioner,http://hl7.org/fhir/StructureDefinition/PractitionerRole,http://hl7.org/fhir/StructureDefinition/Patient,http://hl7.org/fhir/StructureDefinition/RelatedPerson,http://hl7.org/fhir/StructureDefinition/Organization)`:0..1). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)).
Element `EvidenceReport.editor` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.editor` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)).
Element `EvidenceReport.reviewer` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.reviewer` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `EvidenceReport.endorser` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.endorser` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (see [Clinical Reasoning Module](https://hl7.org/fhir/clinicalreasoning-module.html)). See guidance around (not) making local changes to elements [here](https://hl7.org/fhir/canonicalreso.html#localization).
Element `EvidenceReport.relatesTo` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). A document is a version specific composition.
Element `EvidenceReport.relatesTo.code` is part of an existing definition because parent element `EvidenceReport.relatesTo` requires a cross-version extension. Element `EvidenceReport.relatesTo.code` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.code` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If this document appends another document, then the document cannot be fully understood without also accessing the referenced document.
Element `EvidenceReport.relatesTo.target` is part of an existing definition because parent element `EvidenceReport.relatesTo` requires a cross-version extension. Element `EvidenceReport.relatesTo.target` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.relatesTo.target.url` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.url` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.url` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.relatesTo.target.identifier` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.identifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.identifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.relatesTo.target.display` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.display` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.display` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.relatesTo.target.resource` is part of an existing definition because parent element `EvidenceReport.relatesTo.target` requires a cross-version extension. Element `EvidenceReport.relatesTo.target.resource` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target.resource` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section.title` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.title` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.title` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title, or documents that only have a single section.
Element `EvidenceReport.section.focus` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.focus` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.focus` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The code identifies the section for an automated processor of the document. This is particularly relevant when using profiles to control the structure of the document. If the section has content (instead of sub-sections), the section.code does not change the meaning or interpretation of the resource that is the content of the section in the comments for the section.code.
Element `EvidenceReport.section.focusReference` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.focusReference` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.focusReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section.author` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.author` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.author` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section.text` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.text` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.text` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Document profiles may define what content should be represented in the narrative.
Element `EvidenceReport.section.mode` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.mode` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.mode` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
Element `EvidenceReport.section.orderedBy` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.orderedBy` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.orderedBy` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Applications SHOULD render ordered lists in the order provided, but MAY allow users to re-order based on their own preferences as well. If there is no order specified, the order is unknown, though there may still be some order.
Element `EvidenceReport.section.entryClassifier` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryClassifier` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryClassifier` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section.entryReference` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryReference` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryReference` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). If there are no entries in the list, an emptyReason SHOULD be provided.
Element `EvidenceReport.section.entryQuantity` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.entryQuantity` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryQuantity` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element).
Element `EvidenceReport.section.emptyReason` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.emptyReason` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.emptyReason` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). The various reasons for an empty section make a significant interpretation to its interpretation. Note that this code is for use when the entire section content has been suppressed, and not for when individual items are omitted - implementers may consider using a text note or a flag on an entry in these cases.
Element `EvidenceReport.section.section` is part of an existing definition because parent element `EvidenceReport.section` requires a cross-version extension. Element `EvidenceReport.section.section` is not mapped to FHIR R4, since FHIR R5 `EvidenceReport` is not mapped. Element `EvidenceReport.section.section` has no mapping targets in FHIR R4. Typically, this is because the element has been added (is a new element). Nested sections are primarily used to help human readers navigate to particular portions of the document.