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

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

ConceptMap: R4BEvidenceReportElementMapToR3

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

This ConceptMap represents cross-version mappings for elements from a FHIR R4B EvidenceReport to FHIR STU3.

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


Group 1 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to http://hl7.org/fhir/StructureDefinition/Basic|3.0.2

Source CodeRelationshipTarget CodeComment
EvidenceReport.meta (meta)is equivalent toBasic.metaElement matches Basic element path `Basic.meta` (`Resource.meta`), use that element instead. Element `EvidenceReport.meta` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.meta` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.implicitRules (implicitRules)is equivalent toBasic.implicitRulesElement matches Basic element path `Basic.implicitRules` (`Resource.implicitRules`), use that element instead. Element `EvidenceReport.implicitRules` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.implicitRules` has no mapping targets in FHIR STU3. 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 it's narrative along with other profiles, value sets, etc.
EvidenceReport.language (language)is equivalent toBasic.languageElement matches Basic element path `Basic.language` (`Resource.language`), use that element instead. Element `EvidenceReport.language` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.language` has no mapping targets in FHIR STU3. 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 toBasic.textElement matches Basic element path `Basic.text` (`DomainResource.text`), use that element instead. Element `EvidenceReport.text` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.text` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
EvidenceReport.contained (contained)is equivalent toBasic.containedElement matches Basic element path `Basic.contained` (`DomainResource.contained`), use that element instead. Element `EvidenceReport.contained` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.contained` has no mapping targets in FHIR STU3. 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 toBasic.identifierElement matches Basic element path `Basic.identifier` (`Basic.identifier`), use that element instead. Element `EvidenceReport.identifier` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.identifier` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: Canonical identifier for this EvidenceReport, represented as a globally unique URI (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.url (url)maps to wider conceptExtension (R4B: Canonical identifier for this EvidenceReport, represented as a globally unique URI (new))Element `EvidenceReport.url` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.url` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: draft | active | retired | unknown (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.status (status)maps to wider conceptExtension (R4B: draft | active | retired | unknown (new))Element `EvidenceReport.status` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.status` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Allows filtering of summaries that are appropriate for use versus not.

Group 4 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: The context that the content is intended to support (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.useContext (useContext)maps to wider conceptExtension (R4B: The context that the content is intended to support (new))Element `EvidenceReport.useContext` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.useContext` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: Identifiers for articles that may relate to more than one evidence report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.relatedIdentifier (relatedIdentifier)maps to wider conceptExtension (R4B: Identifiers for articles that may relate to more than one evidence report (new))Element `EvidenceReport.relatedIdentifier` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.relatedIdentifier` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: Citation for this report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.citeAs[x] (citeAs[x])maps to wider conceptExtension (R4B: Citation for this report (new))Element `EvidenceReport.citeAs[x]` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.citeAs[x]` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: Kind of report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.type (type)maps to wider conceptExtension (R4B: Kind of report (new))Element `EvidenceReport.type` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 8 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Used for footnotes and annotations (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.note (note)maps to wider conceptExtension (R4B: Used for footnotes and annotations (new))Element `EvidenceReport.note` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 9 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Link, description or reference to artifact associated with the report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.relatedArtifact (relatedArtifact)maps to wider conceptExtension (R4B: Link, description or reference to artifact associated with the report (new))Element `EvidenceReport.relatedArtifact` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.relatedArtifact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 10 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Focus of the report (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.subject (subject)maps to wider conceptExtension (R4B: Focus of the report (new))Element `EvidenceReport.subject` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:characteristic (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.subject.characteristic.code (code)maps to wider conceptExtension.extension:characteristic.extension:code (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.code` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:characteristic.extension:value (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.value[x]` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:characteristic.extension:exclude (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.exclude` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.subject.characteristic.period (period)maps to wider conceptExtension.extension:characteristic.extension:period (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.characteristic.period` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.subject.note (note)maps to wider conceptExtension.extension:note (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.subject.note` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 11 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Name of the publisher (organization or individual) (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.publisher (publisher)maps to wider conceptExtension (R4B: Name of the publisher (organization or individual) (new))Element `EvidenceReport.publisher` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.publisher` has no mapping targets in FHIR STU3. 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|4.3.0 to R4B: Contact details for the publisher (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.contact (contact)maps to wider conceptExtension (R4B: Contact details for the publisher (new))Element `EvidenceReport.contact` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.contact` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Group 13 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Who authored the content (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.author (author)maps to wider conceptExtension (R4B: Who authored the content (new))Element `EvidenceReport.author` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.author` has no mapping targets in FHIR STU3. 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/Patient,http://hl7.org/fhir/StructureDefinition/RelatedPerson)`:0..1). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Group 14 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Who edited the content (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.editor (editor)maps to wider conceptExtension (R4B: Who edited the content (new))Element `EvidenceReport.editor` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.editor` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Group 15 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Who reviewed the content (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.reviewer (reviewer)maps to wider conceptExtension (R4B: Who reviewed the content (new))Element `EvidenceReport.reviewer` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.reviewer` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Group 16 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Who endorsed the content (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.endorser (endorser)maps to wider conceptExtension (R4B: Who endorsed the content (new))Element `EvidenceReport.endorser` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.endorser` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Extensions to ContactDetail include: contactReference, contactAddress, and contributionTime (Details at: http://build.fhir.org/clinicalreasoning-module.html).

Group 17 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Relationships to other compositions/documents (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.relatesTo (relatesTo)maps to wider conceptExtension (R4B: Relationships to other compositions/documents (new))Element `EvidenceReport.relatesTo` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:code (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.code` has no mapping targets in FHIR STU3. 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[x] (target[x])maps to wider conceptExtension.extension:target (R4B: Target of the relationship (new))Element `EvidenceReport.relatesTo.target[x]` is part of an existing definition because parent element `EvidenceReport.relatesTo` requires a cross-version extension. Element `EvidenceReport.relatesTo.target[x]` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.relatesTo.target[x]` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).

Group 18 Mapping from http://hl7.org/fhir/StructureDefinition/EvidenceReport|4.3.0 to R4B: Composition is broken into sections (new)version: 0.1.0)

Source CodeRelationshipTarget CodeComment
EvidenceReport.section (section)maps to wider conceptExtension (R4B: Composition is broken into sections (new))Element `EvidenceReport.section` is not mapped to FHIR STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.section.title (title)maps to wider conceptExtension.extension:title (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.title` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:focus (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.focus` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:focusReference (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.focusReference` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.section.author (author)maps to wider conceptExtension.extension:author (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.author` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.section.text (text)maps to wider conceptExtension.extension:text (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.text` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:mode (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.mode` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:orderedBy (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.orderedBy` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:entryClassifier (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryClassifier` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.section.entryReference (entryReference)maps to wider conceptExtension.extension:entryReference (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryReference` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:entryQuantity (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.entryQuantity` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
EvidenceReport.section.emptyReason (emptyReason)maps to wider conceptExtension.extension:emptyReason (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.emptyReason` has no mapping targets in FHIR STU3. 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 conceptExtension.extension:section (R4B: 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 STU3, since FHIR R4B `EvidenceReport` is not mapped. Element `EvidenceReport.section.section` has no mapping targets in FHIR STU3. 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.