import { CodeableConcept } from './CodeableConcept.js';
import { Device } from './Device.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { Group } from './Group.js';
import { Narrative } from './Narrative.js';
import { Organization } from './Organization.js';
import { Patient } from './Patient.js';
import { Practitioner } from './Practitioner.js';
import { PractitionerRole } from './PractitionerRole.js';
import { Quantity } from './Quantity.js';
import { Reference } from './Reference.js';
import { RelatedPerson } from './RelatedPerson.js';
import { Resource } from './Resource.js';
export interface EvidenceReport_Section {
    /**
     * @description Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
     * @short Unique id for inter-element referencing
     */
    id?: string;
    /**
     * @description 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.
     * @comment 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.
     * @short Additional content defined by implementations
     */
    extension?: Extension[];
    /**
     * @description 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 andor 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).
     * @comment 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.
     * @short Extensions that cannot be ignored even if unrecognized
     */
    modifierExtension?: Extension[];
    /**
     * @description 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.
     * @comment 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.
     * @short Label for section (e.g. for ToC)
     */
    title?: FhirPrimitive<string>;
    /**
     * @description A code identifying the kind of content contained within the section. This should be consistent with the section title.
     * @comment 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.
     * @short Classification of section (recommended)
     */
    focus?: CodeableConcept;
    /**
     * @description A definitional Resource identifying the kind of content contained within the section. This should be consistent with the section title.
     * @short Classification of section by Resource
     */
    focusReference?: Reference<Resource>;
    /**
     * @description Identifies who is responsible for the information in this section, not necessarily who typed it in.
     * @short Who andor what authored the section
     */
    author?: Reference<Patient | Practitioner | PractitionerRole | RelatedPerson | Device | Group | Organization>[];
    /**
     * @description 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.
     * @comment Document profiles may define what content should be represented in the narrative.
     * @short Text summary of the section, for human interpretation
     */
    text?: Narrative;
    /**
     * @description 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.
     * @comment This element is labeled as a modifier because a change list must not be misunderstood as a complete list.
     * @short working | snapshot | changes
     */
    mode?: FhirPrimitive<string>;
    /**
     * @description Specifies the order applied to the items in the section entries.
     * @comment 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.
     * @short Order of section entries
     */
    orderedBy?: CodeableConcept;
    /**
     * @description Specifies any type of classification of the evidence report.
     * @short Extensible classifiers as content
     */
    entryClassifier?: CodeableConcept[];
    /**
     * @description A reference to the actual resource from which the narrative in the section is derived.
     * @comment If there are no entries in the list, an emptyReason SHOULD be provided.
     * @short Reference to resources as content
     */
    entryReference?: Reference<Resource>[];
    /**
     * @description Quantity as content.
     * @short Quantity as content
     */
    entryQuantity?: Quantity[];
    /**
     * @description If the section is empty, why the list is empty. An empty section typically has some text explaining the empty reason.
     * @comment 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.
     * @short Why the section is empty
     */
    emptyReason?: CodeableConcept;
    /**
     * @description A nested sub-section within this section.
     * @comment Nested sections are primarily used to help human readers navigate to particular portions of the document.
     * @short Nested Section
     */
    section?: any[];
}
//# sourceMappingURL=EvidenceReport_Section.d.ts.map