pub struct EvidenceReportSection {Show 27 fields
pub id: Option<String>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub title: Option<String>,
pub title_ext: Option<FieldExtension>,
pub focus: Option<CodeableConcept>,
pub focus_ext: Option<FieldExtension>,
pub focus_reference: Option<Reference>,
pub focus_reference_ext: Option<FieldExtension>,
pub author: Vec<Option<Reference>>,
pub author_ext: Vec<Option<FieldExtension>>,
pub text: Option<Narrative>,
pub text_ext: Option<FieldExtension>,
pub mode: Option<ListMode>,
pub mode_ext: Option<FieldExtension>,
pub ordered_by: Option<CodeableConcept>,
pub ordered_by_ext: Option<FieldExtension>,
pub entry_classifier: Vec<Option<CodeableConcept>>,
pub entry_classifier_ext: Vec<Option<FieldExtension>>,
pub entry_reference: Vec<Option<Reference>>,
pub entry_reference_ext: Vec<Option<FieldExtension>>,
pub entry_quantity: Vec<Option<Quantity>>,
pub entry_quantity_ext: Vec<Option<FieldExtension>>,
pub empty_reason: Option<CodeableConcept>,
pub empty_reason_ext: Option<FieldExtension>,
pub section: Vec<Option<EvidenceReportSection>>,
pub section_ext: Vec<Option<FieldExtension>>,
}Expand description
Sub-fields of the section field in EvidenceReport
Fields§
§id: Option<String>Unique id for inter-element referencing
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
extension: Vec<Extension>Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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.
modifier_extension: Vec<Extension>Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element’s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
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.
title: Option<String>Label for section (e.g. for ToC)
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.
title_ext: Option<FieldExtension>Extension field.
focus: Option<CodeableConcept>ReportSectionType; Classification of section (recommended)
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.
focus_ext: Option<FieldExtension>Extension field.
focus_reference: Option<Reference>Classification of section by Resource
A definitional Resource identifying the kind of content contained within the section. This should be consistent with the section title.
focus_reference_ext: Option<FieldExtension>Extension field.
Who and/or what authored the section
Identifies who is responsible for the information in this section, not necessarily who typed it in.
Extension field.
text: Option<Narrative>Text summary of the section, for human interpretation
A human-readable narrative that contains the attested content of the section, used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is peferred to contain sufficient detail to make it acceptable for a human to just read the narrative.
Document profiles may define what content should be represented in the narrative.
text_ext: Option<FieldExtension>Extension field.
mode: Option<ListMode>SectionMode; working | snapshot | changes
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.
mode_ext: Option<FieldExtension>Extension field.
ordered_by: Option<CodeableConcept>SectionEntryOrder; Order of section entries
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.
ordered_by_ext: Option<FieldExtension>Extension field.
entry_classifier: Vec<Option<CodeableConcept>>EvidenceClassifier; Extensible classifiers as content
Specifies any type of classification of the evidence report.
entry_classifier_ext: Vec<Option<FieldExtension>>Extension field.
entry_reference: Vec<Option<Reference>>Reference to resources as content
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.
entry_reference_ext: Vec<Option<FieldExtension>>Extension field.
entry_quantity: Vec<Option<Quantity>>Quantity as content
Quantity as content.
entry_quantity_ext: Vec<Option<FieldExtension>>Extension field.
empty_reason: Option<CodeableConcept>SectionEmptyReason; Why the section is empty
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.
empty_reason_ext: Option<FieldExtension>Extension field.
section: Vec<Option<EvidenceReportSection>>Nested Section
A nested sub-section within this section.
Nested sections are primarily used to help human readers navigate to particular portions of the document.
section_ext: Vec<Option<FieldExtension>>Extension field.
Implementations§
Source§impl EvidenceReportSection
impl EvidenceReportSection
Sourcepub fn builder() -> EvidenceReportSectionBuilder
pub fn builder() -> EvidenceReportSectionBuilder
Start building a new instance
Trait Implementations§
Source§impl Clone for EvidenceReportSection
impl Clone for EvidenceReportSection
Source§fn clone(&self) -> EvidenceReportSection
fn clone(&self) -> EvidenceReportSection
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more