STARS Implementation Guide
0.6.1 - release

This page is part of the Csiro Stars (v0.6.1: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version. For a full list of available versions, see the Directory of published versions

Bundle - Task

Overview

Tasks are used to communicate the status and progression of testing between the ServiceRequest and the resulting DiagnosticReport. They provide updates at key stages of the workflow, allowing both sending and receiving systems to track the lifecycle of a request. Customisations have been made to the standard FHIR resources, known as Profiles.

The Task Bundle will typically contain:

You will find some examples of the full bundle on Artifacts under the QA Bundle for Task name.

Request Received Task Indicates that the ServiceRequest has been successfully received. This task may also include associated submission documentation (e.g. job receipt/SAN).

Specimen Received Task Confirms that the physical samples linked to the ServiceRequest have been received by the testing laboratory.

STARS Message WorkflowRequesting LaboratoryRequesting LaboratoryTesting LaboratoryTesting LaboratoryRequest with specimen testing request (Bundle-ServiceRequest)Request received, submission paperwork attached (Bundle-Task-RequestReceived)Specimen received (Bundle-Task-SpecimenReceived)Report results (Bundle-DiagnosticReport)
Send specimen to Lab, receive results from testing

Task CSV Model

Task CSV ModelTaskBundlemessageheader_idmessageheader_eventmessageheader_receivermessageheader_sendermessageheader_author_identifiermessageheader_author_fullnamemessageheader_author_emailtask_requisitiontask_codetask_statustask_intenttask_input_specimen_identifierstask_media_titletask_media_docstatusLegend:required field
Model task

Required Fields

Name (Required) Definition Value
messageheader_event Message type: MUST be Task ValueSet: MessageTypeValueSet
messageheader_receiver receiver node node username
messageheader_sender sender node node username or senders username
messageheader_author_identifier   stars username
messageheader_author_fullname   Free-text
messageheader_author_email   Free-text
task_requisition Which submissions or job requisitions the report relates to. Free-text
task_code Identifies the task type such as request-received or specimen-received ValueSet: StarsTaskTypeValueSet
task_status FHIR status of this task. ValueSet: Task Status
task_intent FHIR intent of this task. ValueSet: Task Intent

Optional Fields

Name (Optional) Definition Value
messageheader_id Message Identifier: UUID Free-text (UUID)
task_input_specimen_identifiers List of identifiers included that this task pertains to, separated by ; Free-text
task_media_title Filename of the attached document. Free-text
task_media_docstatus Status of the attached document. ValueSet: CompositionStatus

Task Basic Model (Intermediary Format)

This data structure is used internally as an intermediary format when converting between CSV and FHIR messages and may help to understand the structure of the complete FHIR Profiles. See the Artifact - Resource Profiles for more detailed information.

Task Basic ModelMessageHeadermessageheader_idmessageheader_eventmessageheader_receivermessageheader_sendermessageheader_author_identifiermessageheader_author_fullnamemessageheader_author_emailtask []Taskrequisitionstatusintentcodeinput_specimen_identifiers []media_titlemedia_docstatusLegend:required field
Task basic model used to convert between CSV and FHIR.