Demos
Others titles
- FHIR Task Resource
- Electronic Health Records Exchange Through FHIR
Keywords
- FHIR
- HL7
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
Task
A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity.
Get The Data
- Research
Non-Commercial, 
Share-Alike, 
Attribution Free Forever - Commercial
Commercial Use, 
Remix & Adapt, 
White Label
Log in to download
Description
Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real-world actions by one or more humans. Some orders can only be processed when other real-world actions happen, such as a patient presenting themselves so that the action to be performed can actually be performed. Often these real-world dependencies are only implicit in the order details.
Tasks start in a Created state. Once they have been assigned to an owner they transition to the Ready state, indicating that they are ready to be performed. Once the owner initiates activity on the task, the task transitions to the In Progress state, indicating that work is being performed. Upon normal completion, the task enters the Completed state. If there is a failure during the task execution that prevents the task from being completed, it can also enter a Failed state, indicating an abnormal termination of the task. A task in any non-terminal state may also be Cancelled, representing an abnormal termination of the task due to external forces, rather than an error condition.
Tasks in any non-terminal state (Created, Ready, In Progress) can be suspended and resumed. When a task is suspended, it is typically resumed in the state it was in when it was originally suspended. Suspending a task suspends all of its children as well. Resuming a task resumes all of its children.
An In-progress task can also be stopped, returning it to a Ready state. This may be in preparation for delegation or reassignment (e.g., because it cannot be completed by the current owner), to restart a task due to a temporary failure (e.g., to reattempt completion of the activity), or in preparation to allow others to claim the task.
The task history allows applications monitoring the state of a workflow to identify tasks that are long-running, perhaps stuck in some queue, to enable management activities that could ensure completion. It also enables tracking of task statistics such as wait time, or time in progress, or time to completion, enabling capture of important task metrics in support of optimization and quality improvement.
About this Dataset
Data Info
| Date Created | 2018-09-20 |
|---|---|
| Last Modified | 2023-03-26 |
| Version | 5.0.0 |
| Update Frequency |
Annual |
| Temporal Coverage |
N/A |
| Spatial Coverage |
United States |
| Source | John Snow Labs; Health Level Seven International; |
| Source License URL | |
| Source License Requirements |
N/A |
| Source Citation |
N/A |
| Keywords | FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR |
| Other Titles | FHIR Task Resource, Electronic Health Records Exchange Through FHIR |
Data Fields
| Name | Description | Type | Constraints |
|---|---|---|---|
| Concept_Name | Name of the concept in the FHIR structure | string | required : 1 |
| Computer_Ready_Name | A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this. | string | - |
| Type | The type the structure describes. | string | - |
| Dollar_Ref | The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced. | string | - |
| Description | A free text natural language description of the structure and its use | string | - |
| Items | The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value. | string | - |
| Enum | The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value. | string | - |
| Required | The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value. | string | - |
| Const | The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword. | string | - |
Data Preview
| Concept Name | Computer Ready Name | Type | Dollar Ref | Description | Items | Enum | Required | Const |
| Task;resourceType;;;This is a Task resource;;;;Task | ||||||||
| Task;id;;#/definitions/id;The logical id of the resource | as used in the URL for the resource. Once assigned | this value never changes.;;;; | ||||||
| Task;meta;;#/definitions/Meta;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.;;;; | ||||||||
| Task;implicitRules;;#/definitions/uri;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.;;;; | ||||||
| Task;_implicitRules;;#/definitions/Element;Extensions for implicitRules;;;; | ||||||||
| Task;language;;#/definitions/code;The base language in which the resource is written.;;;; | ||||||||
| Task;_language;;#/definitions/Element;Extensions for language;;;; | ||||||||
| Task;text;;#/definitions/Narrative;"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.";;;; | |||||||
| Task;contained;array;;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.;{'$ref': '#/definitions/ResourceList'};;; | |||||||
| Task;extension;array;;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.;{'$ref': '#/definitions/Extension'};;; |
