AU eRequesting Implementation Guide
1.0.0-ci-build - CI Build
AU eRequesting Implementation Guide, published by HL7 Australia. This guide is not an authorized publication; it is the continuous build for version 1.0.0-ci-build built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7au/au-fhir-erequesting/ and changes regularly. See the Directory of published versions
| Official URL: http://terminology.hl7.org.au/ValueSet/au-erequesting-task-businessstatus | Version: 1.0.0-ci-build | |||
| Standards status: Draft | Maturity Level: 1 | Computable Name: AUeRequestingTaskBusinessStatus | ||
| Other Identifiers: OID:2.16.840.1.113883.2.3.4.2.4.39 | ||||
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 business status values used in the Australian eRequesting context.
References
Changes since version 1.0.0-ballot:
Profile: https://healthterminologies.gov.au/fhir/StructureDefinition/composed-value-set-4
http://terminology.hl7.org.au/CodeSystem/task-business-status version 📦6.0.0-ci-build
Expansion performed internally based on codesystem Task Business Status v6.0.0-ci-build (CodeSystem)
This value set contains 10 concepts
| System | Code | Display (en) | Definition | JSON | XML |
http://terminology.hl7.org.au/CodeSystem/task-business-status | service-booked | Service booked | Service has been booked. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | request-claimed | Request claimed | The task has been cancelled as the request has been claimed by another filler. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | request-cancelled-placer | Request cancelled by placer | The task has been cancelled as the request has been cancelled by the placer. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | cancel-handled | Cancel handled | Cancelled task has been handled by the filler. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | request-data-issue | Request rejected with data issue | Rejected fulfilment task due to an issue with the request data. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | preliminary-results | Preliminary results | There are preliminary results. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | addendum-report-complete | Addendum report complete | Addendum report is complete. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | specimen-collected | Specimen collected | The specimen has been collected. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | pathology-in-lab | Pathology specimen in lab | Specimen is in a pathology lab. | ||
http://terminology.hl7.org.au/CodeSystem/task-business-status | image-acquired | Image acquired | Image acquisition complete. |
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 |