pub struct TaskInner {Show 74 fields
pub id: Option<String>,
pub meta: Option<Meta>,
pub implicit_rules: Option<String>,
pub language: Option<String>,
pub text: Option<Narrative>,
pub contained: Vec<Resource>,
pub extension: Vec<Extension>,
pub modifier_extension: Vec<Extension>,
pub identifier: Vec<Option<Identifier>>,
pub identifier_ext: Vec<Option<FieldExtension>>,
pub instantiates_canonical: Option<String>,
pub instantiates_canonical_ext: Option<FieldExtension>,
pub instantiates_uri: Option<String>,
pub instantiates_uri_ext: Option<FieldExtension>,
pub based_on: Vec<Option<Reference>>,
pub based_on_ext: Vec<Option<FieldExtension>>,
pub group_identifier: Option<Identifier>,
pub group_identifier_ext: Option<FieldExtension>,
pub part_of: Vec<Option<Reference>>,
pub part_of_ext: Vec<Option<FieldExtension>>,
pub status: TaskStatus,
pub status_ext: Option<FieldExtension>,
pub status_reason: Option<CodeableReference>,
pub status_reason_ext: Option<FieldExtension>,
pub business_status: Option<CodeableConcept>,
pub business_status_ext: Option<FieldExtension>,
pub intent: TaskIntent,
pub intent_ext: Option<FieldExtension>,
pub priority: Option<RequestPriority>,
pub priority_ext: Option<FieldExtension>,
pub do_not_perform: Option<bool>,
pub do_not_perform_ext: Option<FieldExtension>,
pub code: Option<CodeableConcept>,
pub code_ext: Option<FieldExtension>,
pub description: Option<String>,
pub description_ext: Option<FieldExtension>,
pub focus: Option<Reference>,
pub focus_ext: Option<FieldExtension>,
pub for: Option<Reference>,
pub for_ext: Option<FieldExtension>,
pub encounter: Option<Reference>,
pub encounter_ext: Option<FieldExtension>,
pub requested_period: Option<Period>,
pub requested_period_ext: Option<FieldExtension>,
pub execution_period: Option<Period>,
pub execution_period_ext: Option<FieldExtension>,
pub authored_on: Option<DateTime>,
pub authored_on_ext: Option<FieldExtension>,
pub last_modified: Option<DateTime>,
pub last_modified_ext: Option<FieldExtension>,
pub requester: Option<Reference>,
pub requester_ext: Option<FieldExtension>,
pub requested_performer: Vec<Option<CodeableReference>>,
pub requested_performer_ext: Vec<Option<FieldExtension>>,
pub owner: Option<Reference>,
pub owner_ext: Option<FieldExtension>,
pub performer: Vec<Option<TaskPerformer>>,
pub performer_ext: Vec<Option<FieldExtension>>,
pub location: Option<Reference>,
pub location_ext: Option<FieldExtension>,
pub reason: Vec<Option<CodeableReference>>,
pub reason_ext: Vec<Option<FieldExtension>>,
pub insurance: Vec<Option<Reference>>,
pub insurance_ext: Vec<Option<FieldExtension>>,
pub note: Vec<Option<Annotation>>,
pub note_ext: Vec<Option<FieldExtension>>,
pub relevant_history: Vec<Option<Reference>>,
pub relevant_history_ext: Vec<Option<FieldExtension>>,
pub restriction: Option<TaskRestriction>,
pub restriction_ext: Option<FieldExtension>,
pub input: Vec<Option<TaskInput>>,
pub input_ext: Vec<Option<FieldExtension>>,
pub output: Vec<Option<TaskOutput>>,
pub output_ext: Vec<Option<FieldExtension>>,
/* private fields */
}Expand description
Fields§
§id: Option<String>Logical id of this artifact
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
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.
meta: Option<Meta>Metadata about the resource
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.
implicit_rules: Option<String>A set of rules under which this content was created
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.
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 and/or 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.
language: Option<String>Language; Language of the resource content
The base language in which the resource is written.
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).
text: Option<Narrative>Text summary of the resource, for human interpretation
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.
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.
contained: Vec<Resource>Contained, inline Resources
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 context/meaning.
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.
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 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.
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
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 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 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).
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.
identifier: Vec<Option<Identifier>>Task Instance Identifier
The business identifier for this task.
identifier_ext: Vec<Option<FieldExtension>>Extension field.
instantiates_canonical: Option<String>Formal definition of task
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.
instantiates_canonical_ext: Option<FieldExtension>Extension field.
instantiates_uri: Option<String>Formal definition of task
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.
instantiates_uri_ext: Option<FieldExtension>Extension field.
based_on: Vec<Option<Reference>>Request fulfilled by this task
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.
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).
based_on_ext: Vec<Option<FieldExtension>>Extension field.
group_identifier: Option<Identifier>Requisition or grouper id
A shared identifier common to multiple independent Task and Request instances that were activated/authorized 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.
group_identifier_ext: Option<FieldExtension>Extension field.
part_of: Vec<Option<Reference>>Composite task
Task that this particular task is part of.
This should usually be 0..1.
part_of_ext: Vec<Option<FieldExtension>>Extension field.
status: TaskStatusTaskStatus; draft | requested | received | accepted | +
The current status of the task.
status_ext: Option<FieldExtension>Extension field.
status_reason: Option<CodeableReference>TaskStatusReason; Reason for current status
An explanation as to why this task is held, failed, was refused, etc.
This applies to the current status. Look at the history of the task to see reasons for past statuses.
status_reason_ext: Option<FieldExtension>Extension field.
business_status: Option<CodeableConcept>TaskBusinessStatus; E.g. “Specimen collected”, “IV prepped”
Contains business-specific nuances of the business state.
business_status_ext: Option<FieldExtension>Extension field.
intent: TaskIntentTaskIntent; unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option
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.
This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances.
In most cases, Tasks will have an intent of “order”.
intent_ext: Option<FieldExtension>Extension field.
priority: Option<RequestPriority>TaskPriority; routine | urgent | asap | stat
Indicates how quickly the Task should be addressed with respect to other requests.
priority_ext: Option<FieldExtension>Extension field.
do_not_perform: Option<bool>True if Task is prohibiting action
If true indicates that the Task is asking for the specified action to not occur.
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.
do_not_perform_ext: Option<FieldExtension>Extension field.
code: Option<CodeableConcept>TaskCode; Task Type
A name or code (or both) briefly describing what the task involves.
The title (eg “My Tasks”, “Outstanding Tasks for Patient X”) should go into the code.
code_ext: Option<FieldExtension>Extension field.
description: Option<String>Human-readable explanation of task
A free-text description of what is to be performed.
description_ext: Option<FieldExtension>Extension field.
focus: Option<Reference>What task is acting on
The request being fulfilled or the resource being manipulated (changed, suspended, etc.) by this task.
If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.).
focus_ext: Option<FieldExtension>Extension field.
for: Option<Reference>Beneficiary of the Task
The entity who benefits from the performance of the service specified in the task (e.g., the patient).
for_ext: Option<FieldExtension>Extension field.
encounter: Option<Reference>Healthcare event during which this task originated
The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created.
encounter_ext: Option<FieldExtension>Extension field.
requested_period: Option<Period>When the task should be performed
Indicates the start and/or end of the period of time when completion of the task is desired to take place.
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 and/or in the Task.restriction.period. Instead, it is used for stand-alone tasks.
requested_period_ext: Option<FieldExtension>Extension field.
execution_period: Option<Period>Start and end time of execution
Identifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end).
execution_period_ext: Option<FieldExtension>Extension field.
Task Creation Date
The date and time this task was created.
Extension field.
last_modified: Option<DateTime>Task Last Modified Date
The date and time of last modification to this task.
last_modified_ext: Option<FieldExtension>Extension field.
requester: Option<Reference>Who is asking for task to be done
The creator of the task.
requester_ext: Option<FieldExtension>Extension field.
requested_performer: Vec<Option<CodeableReference>>TaskPerformerType; Who should perform Task
The kind of participant or specific participant that should perform the task.
requested_performer_ext: Vec<Option<FieldExtension>>Extension field.
owner: Option<Reference>Responsible individual
Party responsible for managing task execution.
Tasks may be created with an owner not yet identified.
owner_ext: Option<FieldExtension>Extension field.
performer: Vec<Option<TaskPerformer>>Who or what performed the task
The entity who performed the requested task.
performer_ext: Vec<Option<FieldExtension>>Extension field.
location: Option<Reference>Where task occurs
Principal physical location where this task is performed.
This should only be specified when the Task to be/being 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.
location_ext: Option<FieldExtension>Extension field.
reason: Vec<Option<CodeableReference>>TaskReason; Why task is needed
A description, code, or reference indicating why this task needs to be performed.
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.
reason_ext: Vec<Option<FieldExtension>>Extension field.
insurance: Vec<Option<Reference>>Associated insurance coverage
Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task.
insurance_ext: Vec<Option<FieldExtension>>Extension field.
note: Vec<Option<Annotation>>Comments made about the task
Free-text information captured about the task as it progresses.
note_ext: Vec<Option<FieldExtension>>Extension field.
relevant_history: Vec<Option<Reference>>Key events in history of the Task
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.
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.
relevant_history_ext: Vec<Option<FieldExtension>>Extension field.
restriction: Option<TaskRestriction>Constraints on fulfillment tasks
If the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned.
Task.restriction can only be present if the Task is seeking fulfillment of another Request resource, and the restriction identifies what subset of the authorization conveyed by the request is supposed to be fulfilled by this Task. A possible example could be a standing order (the request) covering a significant time period and/or individuals, while the Task seeks fulfillment for only a subset of that time-period and a single individual.
restriction_ext: Option<FieldExtension>Extension field.
input: Vec<Option<TaskInput>>Information used to perform task
Additional information that may be needed in the execution of the task.
input_ext: Vec<Option<FieldExtension>>Extension field.
output: Vec<Option<TaskOutput>>Information produced as part of task
Outputs produced by the Task.
output_ext: Vec<Option<FieldExtension>>Extension field.