AU eRequesting Implementation Guide
1.0.0-preview - Preview

AU eRequesting Implementation Guide - Downloaded Version 1.0.0-preview See the Directory of published versions

## ValueSet: AU eRequesting Task Status

Official URL: http://terminology.hl7.org.au/ValueSet/au-erequesting-task-status | Version: 1.0.0-preview
Standards status: Draft | Maturity Level: 1 | Computable Name: AUeRequestingTaskStatus
Other Identifiers: OID:2.16.840.1.113883.2.3.4.2.4.37
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License. HL7 Australia© 2024+; Licensed Under Creative Commons No Rights Reserved.

Task status values used in the Australian eRequesting context.

References

- AU eRequesting Task

Changes since version 1.0.0-ballot:

- No changes

### Logical Definition (CLD)

Profile: `https://healthterminologies.gov.au/fhir/StructureDefinition/composed-value-set-4`

- Include these codes as defined in `http://hl7.org/fhir/task-status` version 📦4.0.1

  Code | Display | Definition
  requested | Requested | The task is ready to be acted upon and action is sought.
  received | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it.
  accepted | Accepted | The potential performer has agreed to execute the task but has not yet started work.
  rejected | Rejected | The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action.
  cancelled | Cancelled | The task was not completed.
  in-progress | In Progress | The task has been started but is not yet complete.
  on-hold | On Hold | The task has been started but work has been paused.
  failed | Failed | The task was attempted but could not be completed due to some error.
  completed | Completed | The task has been completed.

### Expansion

Expansion performed internally based on codesystem TaskStatus v4.0.1 (CodeSystem)

This value set contains 9 concepts

System | Code | Display (en) | Definition | JSON | XML
`http://hl7.org/fhir/task-status` | requested | Requested | The task is ready to be acted upon and action is sought. |  |
`http://hl7.org/fhir/task-status` | received | Received | A potential performer has claimed ownership of the task and is evaluating whether to perform it. |  |
`http://hl7.org/fhir/task-status` | accepted | Accepted | The potential performer has agreed to execute the task but has not yet started work. |  |
`http://hl7.org/fhir/task-status` | rejected | Rejected | The potential performer who claimed ownership of the task has decided not to execute it prior to performing any action. |  |
`http://hl7.org/fhir/task-status` | cancelled | Cancelled | The task was not completed. |  |
`http://hl7.org/fhir/task-status` | in-progress | In Progress | The task has been started but is not yet complete. |  |
`http://hl7.org/fhir/task-status` | on-hold | On Hold | The task has been started but work has been paused. |  |
`http://hl7.org/fhir/task-status` | failed | Failed | The task was attempted but could not be completed due to some error. |  |
`http://hl7.org/fhir/task-status` | completed | Completed | The task has been completed. |  |

Explanation of the columns that may appear on this page:

Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System | The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code | The code (used as the code in the resource instance)
Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition | An explanation of the meaning of the concept
Comments | Additional notes about how to use the code