Generated Narrative: StructureDefinition apix-task Language: en Name Flags Card. Type Description & Constraints Task <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( statusreason-conditional-require )">C 0..* Task A task to be performed Constraints: statusreason-conditional-require #xD; meta 1..1 Meta Metadata about the resource #xD; versionId 1..1 id Version specific identifier #xD; lastUpdated 0..1 instant Automatically updated on every change #xD; text S 1..1 Narrative Human-readable narrative #xD; Slices for identifier S 1..* Identifier Task instance UUID (required) + official regulator procedure number (optional), other identifiers allowed as well Slice: Unordered, Open by value:type, value:system #xD; identifier:TaskInstance S<a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( identifier-is-uuid )">C 1..1 Identifier Technical UUID for this specific Task instance Constraints: identifier-is-uuid #xD; type 1..1 CodeableConcept Description of identifier Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/v2-0203 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: RI #xD; display 1..1 string Representation defined by the system Fixed Value: Resource identifier #xD; identifier:RegulatorProcedureNumber S 0..1 Identifier Official regulator procedure/submission number (EMA, FDA, PMDA, etc.) #xD; system 1..1 uri The namespace for the identifier value Required Pattern: https://ema.europa.eu/procedure #xD; value 1..1 string The actual regulator-assigned procedure number (format varies by authority) #xD; basedOn S 0..* Reference(Resource) Reference to the parent Task (e.g. a response points to the question Task), ordered lineage of Tasks (oldest → newest). #xD; groupIdentifier S 1..1 Identifier Parent/Set ID – groups all Tasks in the same regulatory procedure #xD; statusReason 0..1 CodeableReference() Required if status is rejected or cancelled #xD; businessStatus 0..1 CodeableConcept Detailed regulatory status (e.g., clock-stop) Binding: APIX Regulatory Business Status (example): Detailed regulatory status such as clock-stop #xD; intent 1..1 code unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Required Pattern: proposal #xD; code S 1..1 CodeableConcept Defines the regulatory message type and triggers specific business rules Binding: APIX Submission Types (example): Codes to identify what the task involves. These will typically be specific to a particular workflow. #xD; description 0..0 Human-readable explanation of task #xD; for S 0..1 Reference(Resource) Identifies the medicinal product(s) that is the subject. For multiple products use Group or List FHIR Resource #xD; encounter 0..0 Healthcare event during which this task originated #xD; requestedPeriod S 0..1 Period Requested period for task fulfilment #xD; start S 0..1 dateTime Clock-start / earliest allowed start #xD; end S 0..1 dateTime Deadline / clock-stop date #xD; executionPeriod S 0..1 Period Actual execution period #xD; start S 0..1 dateTime Actual start time #xD; end S 0..1 dateTime Actual completion time #xD; authoredOn 1..1 dateTime Date/time the sender created the Task #xD; lastModified 1..1 dateTime Task Last Modified Date #xD; requester S 1..1 Reference(APIX Organization) Organization that initiated the task #xD; owner S 0..1 Reference(APIX Organization) The Organization accountable for fulfilling the Task. #xD; performer S 0..1 BackboneElement Organization or individual who performed the task #xD; relevantHistory 0..0 Key events in history of the Task #xD; restriction 0..0 Constraints on fulfillment tasks #xD; input S 0..* BackboneElement Input parameters for the task #xD; type S 1..1 CodeableConcept Input type indicates the type of input, such as the code used as a DocumentReference type Binding: APIX CTD/eCTD Section Code System (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. #xD; output S 0..* BackboneElement Output produced by the task #xD; type S 1..1 CodeableConcept Output type indicates the type of output, such as the code used as a DocumentReference type Binding: APIX CTD/eCTD Section Code System (example): Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. #xD; Documentation for this format
HL7 International / Biomedical Research and Regulation
Task profile for APIX regulatory submission workflows
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Last modified date must be greater than or equal to authored-on date.
lastModified.exists().not() or authoredOn.exists().not() or lastModified >= authoredOn
Task.restriction is only allowed if the Task is seeking fulfillment and a focus is specified.
restriction.exists() implies code.coding.where(code='fulfill' and system='http://hl7.org/fhir/CodeSystem/task-code').exists() and focus.exists()
A status reason is required when the status is rejected or cancelled.
((status = 'rejected') or (status = 'cancelled')) implies statusReason.exists()
Entity, Role, or Act,ControlAct[moodCode=INT]
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.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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.
Must have either extensions or value[x], not both
The version specific identifier, as it appears in the version portion of the URL. This value changes when the resource is created, updated, or deleted.
The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes.
When the resource last changed - e.g. when the version changed.
This element is generally omitted in instances submitted in a PUT or POST. Instead, it is populated in the response instance and when retrieving information using a GET. The server / resource manager sets this value; what a client provides is irrelevant. This is equivalent to the HTTP Last-Modified and SHOULD have the same value on a [read](http://hl7.org/fhir/R5/http.html#read) interaction.
Identifies where the resource comes from
A uri that identifies the source system of the resource. This provides a minimal amount of [Provenance](http://hl7.org/fhir/R5/provenance.html#) information that can be used to track or differentiate the source of information in the resource. The source may identify another FHIR server, document, message, database, etc.
The exact use of the source (and the possible implied Provenance.entity.role and agent.role) is left to implementer discretion. Only one nominated source is allowed; for additional provenance details, a full Provenance resource should be used. The source may correspond to Provenance.entity.what[x] or Provenance.agent.who[x], though it may be a more general or abstract reference. This element can be used to indicate where the current master source of a resource that has a canonical URL if the resource is no longer hosted at the canonical URL.
Profiles this resource claims to conform to
A list of profiles (references to [StructureDefinition](http://hl7.org/fhir/R5/structuredefinition.html#) resources) that this resource claims to conform to. The URL is a reference to [StructureDefinition.url](http://hl7.org/fhir/R5/structuredefinition-definitions.html#StructureDefinition.url).
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set.
Security Labels applied to this resource
Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure.
The security labels can be updated without changing the stated version of the resource. The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored.
Security Labels from the Healthcare Privacy and Security Classification System.
Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource.
The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored.
Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
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.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
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).
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.
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.
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.
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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
At least one mandatory technical UUID identifier. A regulator procedure number is optional.
Task instance UUID (required) + official regulator procedure number (optional), other identifiers allowed as well
Technical UUID for this specific Task instance
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.
Identifier.system is always case sensitive.
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [http://hl7.org/fhir/StructureDefinition/rendered-value](http://hl7.org/fhir/extensions/StructureDefinition-rendered-value.html)). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
Organization that issued/manages the identifier.
The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
Official regulator procedure/submission number (EMA, FDA, PMDA, etc.)
The actual regulator-assigned procedure number (format varies by authority)
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.
Enables a formal definition of how the task is to be performed, enabling automation.
Request.instantiatesCanonical, Event.instantiatesCanonical
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.
Enables a formal definition of how the task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation.
Reference to the parent Task (e.g. a response points to the question Task), ordered lineage of Tasks (oldest → newest).
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).
Parent/Set ID – groups all Tasks in the same regulatory procedure
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.
Billing and/or reporting can be linked to whether multiple requests were created as a single unit.
Task that this particular task is part of.
Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task).
draft | requested | received | accepted | +
These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Required if status is rejected or cancelled
Required if status is rejected or cancelled. Reason for current status.
This applies to the current status. Look at the history of the task to see reasons for past statuses.
Codes to identify the reason for current status. These will typically be specific to a particular workflow.
.inboundRelationship[typeCode=SUBJ].source[classCode=CACT, moodCode=EVN, code="status change"].reasonCode
Detailed regulatory status (e.g., clock-stop)
Contains business-specific nuances of the business state.
There's often a need to track substates of a task - this is often variable by specific workflow implementation.
Detailed regulatory status such as clock-stop
.inboundRelationship[typeCode=SUBJ].source[classCode=OBS, moodCode=EVN, code="business status"]
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".
Distinguishes whether the task is a proposal, plan or full order.
Indicates how quickly the Task should be addressed with respect to other requests.
Used to identify the service level expected while performing a task.
If missing, this task should be performed with normal priority
The priority of a task (may affect service level applied to the task).
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.
If true, this element negates the Task. For example, instead of a request to perform a task, it is a request _not_ to perform a task.
Defines the regulatory message type and triggers specific business rules
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.
Codes to identify what the task involves. These will typically be specific to a particular workflow.
A free-text description of what is to be performed.
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.).
Identifies the medicinal product(s) that is the subject. For multiple products use Group or List FHIR Resource
Identifies the medicinal product(s) that is the subject of the process, use Group or List FHIR Resource is there are multiple.
Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.
Healthcare event during which this task originated
The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created.
For some tasks it may be important to know the link between the encounter the task originated within.
.inboundRelationship[typeCode=COMP].source[classCode=PCPR, moodCode=EVN]
The period during which the regulatory timeline (e.g., clock start to decision deadline) for the medicinal product procedure or response will be performed.
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.
The date/time when the regulatory clock starts or the earliest the task may begin.
Example: Day 0 of a marketing-authorisation procedure, validation completion date, etc.
The latest date/time by which the task must be completed.
Example: Day 210 of centralised procedure, response deadline to List of Questions, etc.
If the end of the period is missing, it means that the period is ongoing
The actual time period during which the task was performed (e.g., when validation actually started and when it was completed).
The start of the period. The boundary is inclusive.
If the low element is missing, the meaning is that the low boundary is not known.
The end of the period. If the end of the period is missing, it means no end was known or planned at the time the instance was created. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time.
The end value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has an end value of 2012-02-03.
Starting point for regulatory cycle-time metrics.
Most often used along with lastUpdated to track duration of task to supporting monitoring and management.
The date and time of last modification to this task.
Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
.inboundRelationship[typeCode=SUBJ, ].source[classCode=CACT, moodCode=EVN].effectiveTime
The person or system that **created** the Task and wants the work done. In regulatory context: The Regulatory Authority (e.g., FDA/EMA) or a senior manager initiating a submission review.
Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).
The kind of participant or specific participant that should perform the task.
Use to distinguish tasks on different activity queues.
Event.performer.function, Request.performerType
The Organization accountable for fulfilling the Task.
The organization, person or system currently **responsible** for fulfillng the Task.
Tasks may be created with an owner not yet identified.
Identifies who is expected to perform this task.
Event.performer.actor, Request.performer
Organization or individual who performed the task
Organization or individual who performed the task. Can be different from the Task.owner.
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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
A code or description of the performer of the task.
Codes to identify types of task performers.
The actor or entity who performed the task.
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.
Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).
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.
Indicates why the task is needed. E.g. Suspended because patient admitted to hospital.
Insurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task.
Free-text information captured about the task as it progresses.
.inboundRelationship[typeCode=SUBJ, ].source[classCode=OBS, moodCode=EVN, code="annotation"].value(string)
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.
.inboundRelationship(typeCode=SUBJ].source[classCode=CACT, moodCode=EVN]
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.
Sometimes when fulfillment is sought, you don't want full fulfillment.
Instead of pointing to request, would point to component of request, having these characteristics
Indicates the number of times the requested action should occur.
E.g. order that requests monthly lab tests, fulfillment is sought for 1.
The time-period for which fulfillment is sought. This must fall within the overall time period authorized in the referenced request. E.g. ServiceRequest.occurance[x].
This is distinct from Task.executionPeriod. ExecutionPeriod indicates when the task needs to be initiated, while Task.restriction.period specifies the subset of the overall authorization that this period covers. For example, a MedicationRequest with an overall effective period of 1 year might have a Task whose restriction.period is 2 months (i.e. satisfy 2 months of medication therapy), while the execution period might be 'between now and 5 days from now' - i.e. If you say yes to this, then you're agreeing to supply medication for that 2 month period within the next 5 days. Note that period.high is the due date representing the time by which the task should be completed.
E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months.
For requests that are targeted to more than one potential recipient/target, to identify who is fulfillment is sought for.
Additional information that may be needed for fulfilment of the task in the context of medicinal product regulatory procedures.
Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
Input type indicates the type of input, such as the code used as a DocumentReference type
A code or description indicating how the input is intended to be used as part of the task execution.
If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input.
Inputs are named to enable task automation to bind data and pass it from one task to the next.
Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc.
The value of the input parameter as a basic type.
Outputs produced by the task in the context of medicinal product regulatory procedures.
Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
Output type indicates the type of output, such as the code used as a DocumentReference type
Outputs are named to enable task automation to bind data and pass it from one task to the next.
Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc.
The value of the Output parameter as a basic type.