Definitions for the ehealth-task Profile.
1. Task | |
Definition | A task to be performed. |
Control | 0..* |
Invariants | Defined on this element dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative (: contained.text.empty()) dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources (: contained.contained.empty()) dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource (: contained.where(('#'+id in %resource.descendants().reference).not()).empty()) dom-4: 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()) inv-1: Last modified date must be greater than or equal to authored-on date. (: lastModified.exists().not() or authoredOn.exists().not() or lastModified >= authoredOn) |
2. Task.id | |
Definition | The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. |
Control | 0..1 |
Type | id |
Comments | The only time that a resource does not have an id is when it is being submitted to the server using a create operation. |
3. Task.meta | |
Definition | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. |
Control | 0..1 |
Type | Meta |
4. Task.implicitRules | |
Definition | A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. |
Control | 0..1 |
Type | uri |
Is Modifier | true |
Comments | 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
5. Task.language | |
Definition | The base language in which the resource is written. |
Control | 0..1 |
Binding | A human language. The codes SHALL be taken from Common Languages; other codes may be used where these codes are not suitable Max Binding: All Languages |
Type | code |
Comments | 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). |
6. Task.text | |
Definition | A human-readable narrative that contains a summary of the resource, and may 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. |
Control | 0..1 This element is affected by the following invariants: dom-1 |
Type | Narrative |
Alternate Names | narrative, html, xhtml, display |
Comments | Contained resources do not have 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 in formation is added later. |
7. Task.contained | |
Definition | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. |
Control | 0..* |
Type | Resource |
Alternate Names | inline resources, anonymous resources, contained resources |
Comments | 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. |
8. Task.extension | |
Definition | An Extension |
Control | 0..* |
Type | Extension |
Slicing | This element introduces a set of slices on Task.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
9. Task.extension:category | |
SliceName | category |
Definition | An Extension |
Control | 1..1 This element is affected by the following invariants: ele-1 |
Type | Extension(category) (Extension Type: CodeableConcept) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
10. Task.extension:responsible | |
SliceName | responsible |
Definition | Individual, CareTeam or organization responsible for task execution. |
Control | 1..* This element is affected by the following invariants: ele-1 |
Type | Extension(task-responsible) (Extension Type: Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | ehealth-careteam)) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
11. Task.extension:restrictionCategory | |
SliceName | restrictionCategory |
Definition | The resource is intended for certain category of workflow/responsibility only. |
Control | 1..* This element is affected by the following invariants: ele-1 |
Type | Extension(restriction-category) (Extension Type: CodeableConcept) |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) ext-1: Must have either extensions or value[x], not both (: extension.exists() != value.exists()) |
12. Task.modifierExtension | |
Definition | 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. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content |
Comments | 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. |
13. Task.identifier | |
Definition | The business identifier for this task. |
Note | This is a business identifier, not a resource identifier (see discussion) |
Control | 0..* |
Type | Identifier |
14. Task.definition[x] | |
Definition | A reference to a formal or informal definition of the task. For example, a protocol, a step within a defined workflow definition, etc. |
Control | 0..1 |
Type | Choice of: uri, Reference(ehealth-activitydefinition) |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation) to be associated with a task, enabling automation. |
15. Task.basedOn | |
Definition | BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ProcedureRequest, MedicationRequest, ProcedureRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfil. This latter resource is referenced by FocusOn. For example, based on a ProcedureRequest (= BasedOn), a task is created to fulfil a procedureRequest ( = FocusOn ) to collect a specimen from a patient. |
Control | 0..* |
Type | Reference(Resource) |
16. Task.groupIdentifier | |
Definition | An identifier that links together multiple tasks and other requests that were created in the same context. |
Control | 0..1 |
Type | Identifier |
Requirements | Billing and/or reporting can be linked to whether multiple requests were created as a single unit. |
17. Task.groupIdentifier.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
18. Task.groupIdentifier.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
Slicing | This element introduces a set of slices on Task.groupIdentifier.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
19. Task.groupIdentifier.use | |
Definition | The purpose of this identifier. |
Control | 0..1 |
Binding | Identifies the purpose for this identifier, if known . The codes SHALL be taken from IdentifierUse |
Type | code |
Is Modifier | true |
Requirements | Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. |
Comments | This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. |
20. Task.groupIdentifier.type | |
Definition | A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. |
Control | 0..1 |
Binding | A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. The codes SHALL be taken from Identifier Type Codes; other codes may be used where these codes are not suitable |
Type | CodeableConcept |
Requirements | Allows users to make use of identifiers when the identifier system is not known. |
Comments | 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. |
21. Task.groupIdentifier.system | |
Definition | Establishes the namespace for the value - that is, a URL that describes a set values that are unique. |
Control | 0..1 |
Type | uri |
Requirements | 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. |
Example | General:http://www.acme.com/identifiers/patient |
22. Task.groupIdentifier.value | |
Definition | The portion of the identifier typically relevant to the user and which is unique within the context of the system. |
Control | 0..1 |
Type | string |
Comments | 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 Rendered Value extension. |
Example | General:123456 |
23. Task.groupIdentifier.period | |
Definition | Time period during which identifier is/was valid for use. |
Control | 0..1 |
Type | Period |
24. Task.groupIdentifier.assigner | |
Definition | Organization that issued/manages the identifier. |
Control | 0..1 |
Type | Reference(ehealth-organization) |
Comments | 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. |
25. Task.partOf | |
Definition | Task that this particular task is part of. |
Control | 0..* |
Type | Reference(ehealth-task) |
Requirements | Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). |
Comments | This should usually be 0..1. |
26. Task.status | |
Definition | The current status of the task. |
Control | 1..1 |
Binding | The current status of the task. The codes SHALL be taken from TaskStatus |
Type | code |
Requirements | These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. |
27. Task.statusReason | |
Definition | An explanation as to why this task is held, failed, was refused, etc. |
Control | 0..1 |
Binding | Codes to identify the reason for current status. These will typically be specific to a particular workflow. |
Type | CodeableConcept |
Comments | This applies to the current status. Look at the history of the task to see reasons for past statuses. |
28. Task.businessStatus | |
Definition | Contains business-specific nuances of the business state. |
Control | 0..1 |
Binding | The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. |
Type | CodeableConcept |
Requirements | There's often a need to track substates of a task - this is often variable by specific workflow implementation. |
29. Task.intent | |
Definition | Indicates the "level" of actionability associated with the Task. I.e. Is this a proposed task, a planned task, an actionable task, etc. |
Control | 1..1 |
Binding | Distinguishes whether the task is a proposal, plan or full order The codes SHALL be taken from RequestIntent |
Type | code |
Must Support | true |
Comments | This element is immutable. Proposed tasks, planned tasks, etc. must be distinct instances. In most cases, Tasks will have an intent of "order". |
30. Task.priority | |
Definition | Indicates how quickly the Task should be addressed with respect to other requests. |
Control | 1..1 |
Binding | The task's priority The codes SHALL be taken from RequestPriority |
Type | code |
Must Support | true |
Requirements | Used to identify the service level expected while performing a task. |
Meaning if Missing | If missing, this task should be performed with normal priority |
31. Task.code | |
Definition | A name or code (or both) briefly describing what the task involves. |
Control | 0..1 |
Binding | Codes to identify what the task involves. These will typically be specific to a particular workflow. |
Type | CodeableConcept |
Comments | The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code. |
32. Task.description | |
Definition | A free-text description of what is to be performed. |
Control | 0..1 |
Type | string |
33. Task.focus | |
Definition | The request being actioned or the resource being manipulated by this task. |
Control | 0..1 |
Type | Reference(Resource) |
Requirements | Used to identify the thing to be done. |
Comments | If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.). |
34. Task.for | |
Definition | The entity who benefits from the performance of the service specified in the task (e.g., the patient). |
Control | 0..1 |
Type | Reference(Resource) |
Requirements | 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. |
Alternate Names | Patient |
35. Task.context | |
Definition | The healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. |
Control | 1..1 |
Type | Reference(Encounter | ehealth-episodeofcare) |
Requirements | For some tasks it may be important to know the link between the task or episode of care the task originated within. |
36. Task.executionPeriod | |
Definition | 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). |
Control | 0..1 |
Type | Period |
37. Task.authoredOn | |
Definition | The date and time this task was created. |
Control | 0..1 This element is affected by the following invariants: inv-1 |
Type | dateTime |
Requirements | Most often used along with lastUpdated to track duration of task to supporting monitoring and management. |
Alternate Names | Created Date |
38. Task.lastModified | |
Definition | The date and time of last modification to this task. |
Control | 0..1 This element is affected by the following invariants: inv-1 |
Type | dateTime |
Requirements | Used along with history to track task activity and time in a particular task state. This enables monitoring and management. |
Alternate Names | Update Date |
39. Task.requester | |
Definition | The creator of the task. |
Control | 0..1 |
Type | BackboneElement |
Requirements | Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task). |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
40. Task.requester.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
41. Task.requester.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
42. Task.requester.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | 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. |
43. Task.requester.agent | |
Definition | The device, practitioner, etc. who initiated the task. |
Control | 1..1 |
Type | Reference(ehealth-device | ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) |
Alternate Names | Initiator, Author |
44. Task.requester.onBehalfOf | |
Definition | The organization the device or practitioner was acting on behalf of when they initiated the task. |
Control | 0..1 |
Type | Reference(ehealth-organization) |
Requirements | Practitioners and Devices can be associated with multiple organizations. This element indicates which organization they were acting on behalf of when authoring the request. |
45. Task.performerType | |
Definition | The type of participant that can execute the task. |
Control | 0..* |
Binding | The type(s) of task performers allowed The codes SHOULD be taken from TaskPerformerType |
Type | CodeableConcept |
Requirements | Use to distinguish tasks on different activity queues. |
46. Task.owner | |
Definition | Individual or organization currently responsible for task execution. |
Control | 0..1 |
Type | Reference(ehealth-organization | ehealth-patient | ehealth-practitioner | ehealth-relatedperson) |
Requirements | Identifies who is expected to perform this task. |
Alternate Names | Performer, Executer |
Comments | Tasks may be created with an owner not yet identified. |
47. Task.reason | |
Definition | A description or code indicating why this task needs to be performed. |
Control | 0..1 |
Binding | Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. |
Type | CodeableConcept |
Comments | This should only be included if there is no focus or if it differs from the reason indicated on the focus. |
48. Task.note | |
Definition | Free-text information captured about the task as it progresses. |
Control | 0..* |
Type | Annotation |
49. Task.note.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
50. Task.note.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
Slicing | This element introduces a set of slices on Task.note.extension. The slices are unordered and Open, and can be differentiated using the following discriminators:
|
51. Task.note.author[x] | |
Definition | The individual responsible for making the annotation. |
Control | 0..1 |
Type | Choice of: Reference(ehealth-practitioner | ehealth-patient | ehealth-relatedperson), string |
[x] Note | See Choice of Data Types for further information about how to use [x] |
52. Task.note.time | |
Definition | Indicates when this particular annotation was made. |
Control | 0..1 |
Type | dateTime |
53. Task.note.text | |
Definition | The text of the annotation. |
Control | 1..1 |
Type | string |
54. Task.relevantHistory | |
Definition | 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. |
Control | 0..* |
Type | Reference(ehealth-provenance) |
Alternate Names | Status History |
Comments | 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. |
55. Task.restriction | |
Definition | 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. |
Control | 0..1 |
Type | BackboneElement |
Requirements | Sometimes when fulfillment is sought, you don't want full fulfillment. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
56. Task.restriction.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
57. Task.restriction.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
58. Task.restriction.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | 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. |
59. Task.restriction.repetitions | |
Definition | Indicates the number of times the requested action should occur. |
Control | 0..1 |
Type | positiveInt |
Requirements | E.g. order that requests monthly lab tests, fulfillment is sought for 1. |
60. Task.restriction.period | |
Definition | Over what time-period is fulfillment sought. |
Control | 0..1 |
Type | Period |
Requirements | E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. |
Comments | Note that period.high is the due date representing the time by which the task should be completed. |
61. Task.restriction.recipient | |
Definition | For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? |
Control | 0..* |
Type | Reference(ehealth-patient | ehealth-practitioner | ehealth-relatedperson | Group | ehealth-organization) |
62. Task.input | |
Definition | Additional information that may be needed in the execution of the task. |
Control | 0..* |
Type | BackboneElement |
Requirements | 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. |
Alternate Names | Supporting Information |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
63. Task.input.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
64. Task.input.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
65. Task.input.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | 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. |
66. Task.input.type | |
Definition | A code or description indicating how the input is intended to be used as part of the task execution. |
Control | 1..1 |
Binding | Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concommitent Medications", etc. |
Type | CodeableConcept |
Requirements | Inputs are named to enable task automation to bind data and pass it from one task to the next. |
Alternate Names | Name |
Comments | 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. |
67. Task.input.value[x] | |
Definition | The value of the input parameter as a basic type. |
Control | 1..1 |
Type | Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta |
[x] Note | See Choice of Data Types for further information about how to use [x] |
68. Task.output | |
Definition | Outputs produced by the Task. |
Control | 0..* |
Type | BackboneElement |
Requirements | 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. |
Invariants | Defined on this element ele-1: All FHIR elements must have a @value or children (: hasValue() | (children().count() > id.count())) |
69. Task.output.id | |
Definition | unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. |
Control | 0..1 |
Type | string |
70. Task.output.extension | |
Definition | May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Alternate Names | extensions, user content |
Comments | 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. |
71. Task.output.modifierExtension | |
Definition | 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 that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, 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. |
Control | 0..* |
Type | Extension |
Is Modifier | true |
Alternate Names | extensions, user content, modifiers |
Comments | 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. |
72. Task.output.type | |
Definition | The name of the Output parameter. |
Control | 1..1 |
Binding | 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. |
Type | CodeableConcept |
Requirements | Outputs are named to enable task automation to bind data and pass it from one task to the next. |
Alternate Names | Name |
73. Task.output.value[x] | |
Definition | The value of the Output parameter as a basic type. |
Control | 1..1 |
Type | Choice of: base64Binary, boolean, code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference, SampledData, Signature, Timing, Meta |
[x] Note | See Choice of Data Types for further information about how to use [x] |
Requirements | Task outputs can take any form. |