import { Annotation } from './Annotation.js';
import { BiologicallyDerivedProduct } from './BiologicallyDerivedProduct.js';
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 { Identifier } from './Identifier.js';
import { Location } from './Location.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { Patient } from './Patient.js';
import { Reference } from './Reference.js';
import { Resource } from './Resource.js';
import { ServiceRequest } from './ServiceRequest.js';
import { Specimen_Collection } from './Specimen_Collection.js';
import { Specimen_Container } from './Specimen_Container.js';
import { Specimen_Feature } from './Specimen_Feature.js';
import { Specimen_Processing } from './Specimen_Processing.js';
import { Substance } from './Substance.js';
export interface Specimen {
    /**
     * @description The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
     * @comment Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
     * @short Logical id of this artifact
     */
    id?: string;
    /**
     * @description The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
     * @short Metadata about the resource
     */
    meta?: Meta;
    /**
     * @description A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
     * @comment 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 andor 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.
     * @short A set of rules under which this content was created
     */
    implicitRules?: FhirPrimitive<string>;
    /**
     * @description The base language in which the resource is written.
     * @comment 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).
     * @short Language of the resource content
     */
    language?: FhirPrimitive<string>;
    /**
     * @description A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
     * @comment 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.
     * @short Text summary of the resource, for human interpretation
     */
    text?: Narrative;
    /**
     * @description These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides contextmeaning.
     * @comment 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.
     * @short Contained, inline Resources
     */
    contained?: Resource[];
    /**
     * @description May be used to represent additional information that is not part of the basic definition of the resource. 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 resource and that modifies the understanding of the element that contains it 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 is allowed to 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
     */
    modifierExtension?: Extension[];
    /**
     * @description Id for specimen.
     * @short External Identifier
     */
    identifier?: Identifier[];
    /**
     * @description The identifier assigned by the lab when accessioning specimen(s). This is not necessarily the same as the specimen identifier, depending on local lab procedures.
     * @short Identifier assigned by the lab
     */
    accessionIdentifier?: Identifier;
    /**
     * @description The availability of the specimen.
     * @comment This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
     * @short available | unavailable | unsatisfactory | entered-in-error
     */
    status?: FhirPrimitive<string>;
    /**
     * @description The kind of material that forms the specimen.
     * @comment The type can change the way that a specimen is handled and drives what kind of analyses can properly be performed on the specimen. It is frequently used in diagnostic work flow decision making systems.
     * @short Kind of material that forms the specimen
     */
    type?: CodeableConcept;
    /**
     * @description Where the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance, a biologically-derived product, or a device.
     * @short Where the specimen came from. This may be from patient(s), from a location (e.g., the source of an environmental sample), or a sampling of a substance, a biologically-derived product, or a device
     */
    subject?: Reference<Patient | Group | Device | BiologicallyDerivedProduct | Substance | Location>;
    /**
     * @description Time when specimen is received by the testing laboratory for processing or testing.
     * @short The time when specimen is received by the testing laboratory
     */
    receivedTime?: FhirPrimitive<string>;
    /**
     * @description Reference to the parent (source) specimen which is used when the specimen was either derived from or a component of another specimen.
     * @comment The parent specimen could be the source from which the current specimen is derived by some processing step (e.g. an aliquot or isolate or extracted nucleic acids from clinical samples) or one of many specimens that were combined to create a pooled sample.
     * @short Specimen from which this specimen originated
     */
    parent?: Reference<Specimen>[];
    /**
     * @description Details concerning a service request that required a specimen to be collected.
     * @comment The request may be explicit or implied such with a ServiceRequest that requires a blood draw.
     * @short Why the specimen was collected
     */
    request?: Reference<ServiceRequest>[];
    /**
     * @description This element signifies if the specimen is part of a group or pooled.
     * @short grouped | pooled
     */
    combined?: FhirPrimitive<string>;
    /**
     * @description The role or reason for the specimen in the testing workflow.
     * @short The role the specimen serves
     */
    role?: CodeableConcept[];
    /**
     * @backbone Nested BackboneElement: feature [0..*]
     */
    feature?: Specimen_Feature[];
    /**
     * @backbone Nested BackboneElement: collection [0..1]
     */
    collection?: Specimen_Collection;
    /**
     * @backbone Nested BackboneElement: processing [0..*]
     */
    processing?: Specimen_Processing[];
    /**
     * @backbone Nested BackboneElement: container [0..*]
     */
    container?: Specimen_Container[];
    /**
     * @description A mode or state of being that describes the nature of the specimen.
     * @comment Specimen condition is an observation made about the specimen.  It's a point-in-time assessment.  It can be used to assess its quality or appropriateness for a specific test.
     * @short State of the specimen
     */
    condition?: CodeableConcept[];
    /**
     * @description To communicate any details or issues about the specimen or during the specimen collection. (for example: broken vial, sent with patient, frozen).
     * @short Comments
     */
    note?: Annotation[];
    /**
     * @const Auto-injected fixed value: Specimen
     */
    resourceType: "Specimen";
}
//# sourceMappingURL=Specimen.d.ts.map