Generated Narrative: StructureDefinition ext-R4B-EvidenceReport.section Name Flags Card. Type Description & Constraints Extension 0..* Extension R4B: Composition is broken into sections (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:title 0..1 Extension R4B: Label for section (e.g. for ToC) (new) #xD; url 1..1 uri "title" #xD; value[x] 0..1 string Label for section (e.g. for ToC) #xD; extension:focus 0..1 Extension R4B: Classification of section (recommended) (new) #xD; url 1..1 uri "focus" #xD; value[x] 0..1 CodeableConcept Classification of section (recommended) Binding: R4BEvidenceReportSectionForR3 (0.1.0) (extensible): Evidence Report Section Type. #xD; extension:focusReference 0..1 Extension R4B: Classification of section by Resource (new) #xD; url 1..1 uri "focusReference" #xD; value[x] 0..1 Reference(Cross-version Profile for R4B.Resource for use in FHIR STU3(0.1.0) | Resource) Classification of section by Resource #xD; extension:author 0..* Extension R4B: Who and/or what authored the section (new) #xD; url 1..1 uri "author" #xD; value[x] 0..1 Reference(Cross-version Profile for R4B.Person for use in FHIR STU3(0.1.0) | Person | Cross-version Profile for R4B.Device for use in FHIR STU3(0.1.0) | Device | Cross-version Profile for R4B.Group for use in FHIR STU3(0.1.0) | Group | Cross-version Profile for R4B.Organization for use in FHIR STU3(0.1.0) | Organization) Who and/or what authored the section #xD; extension:text 0..1 Extension R4B: Text summary of the section, for human interpretation (new) #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:_datatype 1..1 Extension DataType slice for a FHIR R4B `Narrative` value #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/_datatype" #xD; value[x] 1..1 string Value of extension Fixed Value: Narrative #xD; extension:status 1..1 Extension R4B: status #xD; url 1..1 uri "status" #xD; value[x] 1..1 code generated | extensions | additional | empty Binding: NarrativeStatus (required) #xD; extension:div 1..1 Extension R4B: div #xD; url 1..1 uri "div" #xD; value[x] 1..1 uri Limited xhtml content #xD; url 1..1 uri "text" #xD; value[x] 0..0 Value of extension #xD; extension:mode 0..1 Extension R4B: working | snapshot | changes (new) #xD; url 1..1 uri "mode" #xD; value[x] 0..1 code working | snapshot | changes Binding: ListMode (required): The processing mode that applies to this section. #xD; extension:orderedBy 0..1 Extension R4B: Order of section entries (new) #xD; url 1..1 uri "orderedBy" #xD; value[x] 0..1 CodeableConcept Order of section entries Binding: List Order Codes (preferred): What order applies to the items in the entry. #xD; extension:entryClassifier 0..* Extension R4B: Extensible classifiers as content (new) #xD; url 1..1 uri "entryClassifier" #xD; value[x] 0..1 CodeableConcept Extensible classifiers as content Binding: R4BEvidenceClassifierCodeForR3 (0.1.0) (extensible): Commonly used classifiers for evidence sets. #xD; extension:entryReference 0..* Extension R4B: Reference to resources as content (new) #xD; url 1..1 uri "entryReference" #xD; value[x] 0..1 Reference(Cross-version Profile for R4B.Resource for use in FHIR STU3(0.1.0) | Resource) Reference to resources as content #xD; extension:entryQuantity 0..* Extension R4B: Quantity as content (new) #xD; url 1..1 uri "entryQuantity" #xD; value[x] 0..1 Quantity Quantity as content #xD; extension:emptyReason 0..1 Extension R4B: Why the section is empty (new) #xD; url 1..1 uri "emptyReason" #xD; value[x] 0..1 CodeableConcept Why the section is empty Binding: List Empty Reasons (preferred): If a section is empty, why it is empty. #xD; extension:section 0..* Extension R4B: Nested Section (new) #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-EvidenceReport.section" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/4.3/StructureDefinition/extension-EvidenceReport.section" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
R4B: Composition is broken into sections (new)
R4B: `EvidenceReport.section` (new:BackboneElement)
This extension is part of the cross-version definitions generated to enable use of the element `EvidenceReport.section` as defined in FHIR R4B in FHIR STU3. The source element is defined as: `EvidenceReport.section` 0..* `BackboneElement` Across FHIR versions, the element set has been mapped as: * R4B `EvidenceReport.section` 0..* `BackboneElement` Following are the generation technical comments: 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).
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).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
R4B: Label for section (e.g. for ToC) (new)
R4B: `EvidenceReport.section.title` (new:string)
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.
Section headings are often standardized for different types of documents. They give guidance to humans on how the document is organized. 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).
Additional Content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
The label for this particular section. This will be part of the rendered content for the document, and is often used to build a table of contents.
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.
R4B: Classification of section (recommended) (new)
R4B: `EvidenceReport.section.focus` (new:CodeableConcept)
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.
Provides computable standardized labels to sections within the document. 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).
A code identifying the kind of content contained within the section. This should be consistent with the section title.
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.
R4B: Classification of section by Resource (new)
R4B: `EvidenceReport.section.focusReference` (new:Reference(Resource))
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).
A definitional Resource identifying the kind of content contained within the section. This should be consistent with the section title.
R4B: Who and/or what authored the section (new)
R4B: `EvidenceReport.section.author` (new:Reference(Person,Device,Group,Organization))
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).
Identifies who is responsible for the content. 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).
Identifies who is responsible for the information in this section, not necessarily who typed it in.
R4B: Text summary of the section, for human interpretation (new)
R4B: `EvidenceReport.section.text` (new:Narrative)
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.
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).
DataType slice for a FHIR R4B `Narrative` value
Slice to indicate the presence of a R4B `Narrative` in FHIR STU3
Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
Element `Narrative.status` is mapped to FHIR STU3 element `Narrative.status` as `Equivalent`.
generated | extensions | additional | empty
The status of the narrative - whether it's entirely generated (from just the defined data or the extensions too), or whether a human authored it and it may contain additional data.
Element `Narrative.div` is mapped to FHIR STU3 element `Narrative.div` as `Equivalent`. The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.
Element `Narrative.div` is mapped to FHIR STU3 element `Narrative.div` as `Equivalent`.
The actual narrative content, a stripped down version of XHTML.
The contents of the html element are an XHTML fragment containing only the basic html formatting elements described in chapters 7-11 and 15 of the HTML 4.0 standard, elements (either name or href), images and internally contained stylesheets. The XHTML content SHALL NOT contain a head, a body, external stylesheet references, scripts, forms, base/link/xlink, frames, iframes and objects.
R4B: `EvidenceReport.section.mode` (new:code)
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.
Sections are used in various ways, and it must be known in what way it is safe to use the entries in them. 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).
How the entry list was prepared - whether it is a working list that is suitable for being maintained on an ongoing basis, or if it represents a snapshot of a list of items from another source, or whether it is a prepared list where items may be marked as added, modified or deleted.
This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
The processing mode that applies to this section.
R4B: `EvidenceReport.section.orderedBy` (new:CodeableConcept)
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.
Important for presentation and rendering. Lists may be sorted to place more important information first or to group related entries. 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).
Specifies the order applied to the items in the section entries.
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.
What order applies to the items in the entry.
R4B: Extensible classifiers as content (new)
R4B: `EvidenceReport.section.entryClassifier` (new:CodeableConcept)
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).
May be used in searching and filtering, or may be the key content of the report. 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).
Specifies any type of classification of the evidence report.
Commonly used classifiers for evidence sets.
R4B: Reference to resources as content (new)
R4B: `EvidenceReport.section.entryReference` (new:Reference(Resource))
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.
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).
A reference to the actual resource from which the narrative in the section is derived.
If there are no entries in the list, an emptyReason SHOULD be provided.
R4B: `EvidenceReport.section.entryQuantity` (new:Quantity)
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).
R4B: `EvidenceReport.section.emptyReason` (new:CodeableConcept)
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.
Allows capturing things like "none exist" or "not asked" which can be important for most lists. 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).
If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
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.
R4B: `EvidenceReport.section.section` (new:EvidenceReport.section)
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.
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).