import { Annotation } from './Annotation.js';
import { CareTeam } from './CareTeam.js';
import { ClaimResponse } from './ClaimResponse.js';
import { CodeableConcept } from './CodeableConcept.js';
import { CodeableReference } from './CodeableReference.js';
import { Coverage } from './Coverage.js';
import { Device } from './Device.js';
import { Encounter } from './Encounter.js';
import { Extension } from './Extension.js';
import { FhirPrimitive } from './FhirPrimitive.js';
import { HealthcareService } from './HealthcareService.js';
import { Identifier } from './Identifier.js';
import { Location } from './Location.js';
import { Meta } from './Meta.js';
import { Narrative } from './Narrative.js';
import { Organization } from './Organization.js';
import { Patient } from './Patient.js';
import { Period } from './Period.js';
import { Practitioner } from './Practitioner.js';
import { PractitionerRole } from './PractitionerRole.js';
import { Provenance } from './Provenance.js';
import { Reference } from './Reference.js';
import { RelatedPerson } from './RelatedPerson.js';
import { Resource } from './Resource.js';
import { Task_Input } from './Task_Input.js';
import { Task_Output } from './Task_Output.js';
import { Task_Performer } from './Task_Performer.js';
import { Task_Restriction } from './Task_Restriction.js';
export interface Task {
    /**
     * @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 The business identifier for this task.
     * @short Task Instance Identifier
     */
    identifier?: Identifier[];
    /**
     * @description The URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task.
     * @short Formal definition of task
     */
    instantiatesCanonical?: FhirPrimitive<string>;
    /**
     * @description The URL pointing to an externally maintained  protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task.
     * @short Formal definition of task
     */
    instantiatesUri?: FhirPrimitive<string>;
    /**
     * @description BasedOn refers to a higher-level authorization that triggered the creation of the task.  It references a "request" resource such as a ServiceRequest, MedicationRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill.  This latter resource is referenced by focus.  For example, based on a CarePlan (= basedOn), a task is created to fulfill a ServiceRequest ( = focus ) to collect a specimen from a patient.
     * @comment Task.basedOn is never the same as Task.focus.  Task.basedOn will typically not be present for 'please fulfill' Tasks as a distinct authorization is rarely needed to request fulfillment.  If the Task is seeking fulfillment of an order, the order to be fulfilled is always communicated using `focus`, never basedOn.  However, authorization may be needed to perform other types of Task actions.  As an example of when both would be present, a Task seeking suspension of a prescription might have a Task.basedOn pointing to the ServiceRequest ordering surgery (which is the driver for suspending the MedicationRequest - which would be the Task.focus).
     * @short Request fulfilled by this task
     */
    basedOn?: Reference<Resource>[];
    /**
     * @description A shared identifier common to multiple independent Task and Request instances that were activatedauthorized more or less simultaneously by a single author.  The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc.  E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.
     * @short Requisition or grouper id
     */
    groupIdentifier?: Identifier;
    /**
     * @description Task that this particular task is part of.
     * @comment This should usually be 0..1.
     * @short Composite task
     */
    partOf?: Reference<Task>[];
    /**
     * @description The current status of the task.
     * @short draft | requested | received | accepted | +
     */
    status: FhirPrimitive<string>;
    /**
     * @description An explanation as to why this task is held, failed, was refused, etc.
     * @comment This applies to the current status.  Look at the history of the task to see reasons for past statuses.
     * @short Reason for current status
     */
    statusReason?: CodeableReference<any>;
    /**
     * @description Contains business-specific nuances of the business state.
     * @short E.g. "Specimen collected", "IV prepped"
     */
    businessStatus?: CodeableConcept;
    /**
     * @description Indicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc.
     * @comment This element is immutable.  Proposed tasks, planned tasks, etc. must be distinct instances.
  
  In most cases, Tasks will have an intent of "order".
     * @short unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
     */
    intent: FhirPrimitive<string>;
    /**
     * @description Indicates how quickly the Task should be addressed with respect to other requests.
     * @short routine | urgent | asap | stat
     */
    priority?: FhirPrimitive<string>;
    /**
     * @description If true indicates that the Task is asking for the specified action to not occur.
     * @comment The attributes provided with the Task qualify what is not to be done. For example, if a requestedPeriod is provided, the 'do not' request only applies within the specified time. If a requestedPerformer is specified then the 'do not' request only applies to performers of that type. Qualifiers include: code, subject, occurrence, requestedPerformer and performer.
  
  In some cases, the Request.code may pre-coordinate prohibition into the requested action. E.g. 'NPO' (nothing by mouth), 'DNR' (do not recussitate). If this happens, doNotPerform SHALL NOT be set to true. I.e. The resource shall not have double negation. (E.g. 'Do not DNR').
  
  doNotPerform should ONLY be used with Tasks that are tightly bounded in time or process phase.  E.g. 'Do not fulfill the midnight dose of medication X tonight due to the early morning scheduled procedure, where the nurse could reasonably check off 'Med X not given at midnight as instructed'.  Similarly, a decision support proposal that a patient should not be given a standard intake questionnaire (because the patient is cognitively impaired) would be marked as 'complete' or 'rejected' when the clinician preps the CarePlan or order set after reviewing the decision support results.  If there is a need to create a standing order to not do something that can't be satisfied by a single 'non-action', but rather an ongoing refusal to perform the function, MedicationRequest, ServiceRequest or some other form of authorization should be used.
     * @short True if Task is prohibiting action
     */
    doNotPerform?: FhirPrimitive<boolean>;
    /**
     * @description A name or code (or both) briefly describing what the task involves.
     * @comment The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.
     * @short Task Type
     */
    code?: CodeableConcept;
    /**
     * @description A free-text description of what is to be performed.
     * @short Human-readable explanation of task
     */
    description?: FhirPrimitive<string>;
    /**
     * @description The request being fulfilled or the resource being manipulated (changed, suspended, etc.) by this task.
     * @comment If multiple resources need to be manipulated, use sub-tasks.  (This ensures that status can be tracked independently for each referenced resource.).
     * @short What task is acting on
     */
    focus?: Reference<Resource>;
    /**
     * @description The entity who benefits from the performance of the service specified in the task (e.g., the patient).
     * @short Beneficiary of the Task
     */
    for?: Reference<Resource>;
    /**
     * @description The healthcare event  (e.g. a patient and healthcare provider interaction) during which this task was created.
     * @short Healthcare event during which this task originated
     */
    encounter?: Reference<Encounter>;
    /**
     * @description Indicates the start andor end of the period of time when completion of the task is desired to take place.
     * @comment This is typically used when the Task is not seeking fulfillment of a focus Request, as in that case the period would be specified on the Request andor in the Task.restriction.period.  Instead, it is used for stand-alone tasks.
     * @short When the task should be performed
     */
    requestedPeriod?: Period;
    /**
     * @description Identifies the time action was first taken against the task (start) andor the time final action was taken against the task prior to marking it as completed (end).
     * @short Start and end time of execution
     */
    executionPeriod?: Period;
    /**
     * @description The date and time this task was created.
     * @short Task Creation Date
     */
    authoredOn?: FhirPrimitive<string>;
    /**
     * @description The date and time of last modification to this task.
     * @short Task Last Modified Date
     */
    lastModified?: FhirPrimitive<string>;
    /**
     * @description The creator of the task.
     * @short Who is asking for task to be done
     */
    requester?: Reference<Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson>;
    /**
     * @description The kind of participant or specific participant that should perform the task.
     * @short Who should perform Task
     */
    requestedPerformer?: CodeableReference<Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson>[];
    /**
     * @description Party responsible for managing task execution.
     * @comment Tasks may be created with an owner not yet identified.
     * @short Responsible individual
     */
    owner?: Reference<Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson>;
    /**
     * @backbone Nested BackboneElement: performer [0..*]
     */
    performer?: Task_Performer[];
    /**
     * @description Principal physical location where this task is performed.
     * @comment This should only be specified when the Task to bebeing performed happens or is expected to happen primarily within the bounds of a single Location.  Other locations (e.g. source, destination, etc.) would either be reflected on the 'basedOn' Request or be conveyed as distinct Task.input values.
     * @short Where task occurs
     */
    location?: Reference<Location>;
    /**
     * @description A description, code, or reference indicating why this task needs to be performed.
     * @comment This will typically not be present for Tasks with a code of 'please fulfill' as, for those, the reason for action is conveyed on the Request pointed to by Task.focus.  Some types of tasks will not need a 'reason'.  E.g. a request to discharge a patient can be inferred to be 'because the patient is ready' and this would not need a reason to be stated on the Task.
     * @short Why task is needed
     */
    reason?: CodeableReference<any>[];
    /**
     * @description Insurance plans, coverage extensions, pre-authorizations andor pre-determinations that may be relevant to the Task.
     * @short Associated insurance coverage
     */
    insurance?: Reference<Coverage | ClaimResponse>[];
    /**
     * @description Free-text information captured about the task as it progresses.
     * @short Comments made about the task
     */
    note?: Annotation[];
    /**
     * @description Links to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task.
     * @comment This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed.  The Provenance for the current version can be retrieved with a _revinclude.
     * @short Key events in history of the Task
     */
    relevantHistory?: Reference<Provenance>[];
    /**
     * @backbone Nested BackboneElement: restriction [0..1]
     */
    restriction?: Task_Restriction;
    /**
     * @backbone Nested BackboneElement: input [0..*]
     */
    input?: Task_Input[];
    /**
     * @backbone Nested BackboneElement: output [0..*]
     */
    output?: Task_Output[];
    /**
     * @const Auto-injected fixed value: Task
     */
    resourceType: "Task";
}
//# sourceMappingURL=Task.d.ts.map