FHIR Artifacts > Structure Definition: Task Profile
Structure Definition: Task Profile
Canonical URL:http://ehealthontario.ca/fhir/StructureDefinition/ca-on-eReferral-profile-Task
Simplifier project page:
Derived from: Task (R4)
Formal Views of Profile Content
Description of Profiles, Differentials, Snapshots and how the different presentations work
Differential View
Hybrid View
Snapshot View
Table View
JSON View
Usage
The Task resource is used as follows in this IG:
a "Process Request" Task (
"Task.code": "process-request"
) SHALL be used by an RMS Target to track and communicate the status of a referral request to the RMS Sourcea "Request for Information" Task (
"Task.code": "request-for-information-for-requester"
) MAY be used by an RMS Target to track and communicate track and communicate a request for information
Each Task SHALL reference the ServiceRequest it is basedOn
.
Notes
.id
- used to uniquely identify the resource
- if a persistent identity for the resource is not available to use when constructing a message Bundle for transmission via Direct Messaging, a UUID SHOULD be used in this element (with a corresponding value in
Bundle.entry.fullUrl
)
.meta.profile
- used to declare conformance to this profile
- populate with a fixed value: `http://ehealthontario.ca/fhir/StructureDefinition/ca-on-eReferral-profile-Task|1.0.0'
.basedOn
- used to associate the Task with the ServiceRequest being performed
- SHALL be populated with a reference to the ServiceRequest being performed
- if the Task is being transmitted via messaging, the referenced ServiceRequest resource SHALL be included in the message as a
Bundle.entry
.status
- for a "Process Request" Task, used to track the status of the ServiceRequest being performed as work progresses through to completion (see: state machine
- for a "Request for Information" Task, used to track the status of the request for information
.businessStatus
- for a "Process Request" Task
businessStatus.text
orbusinessStatus.code
(extensible) MAY be used to communicate deployment specific status information
.intent
- populate with "proposal"
.code
- identifies the type of task
- SHALL always be populated
- with "process-request" for a "Process Request" Task
- with "request-for-information-for-requester" for a "Request for information" Task
.description (for further discussion)
- where
.code
is "request-for-information-for-requester" MAY include a free-text description of what is needed
.authoredOn
- indicates the dateTime that the eReferral was received by the RMS
- usually the same as ServiceRequest.authoredOn, except in cases when ServiceRequest.authoredOn is used to record that a request was signed by the requester before the transmission took place
.lastModified
- indicates the dateTime when an update of note/significance was made to the referral (i.e., related resources such as ServiceRequest, patient, Task, Appointment, etc...)
.owner
- a reference to the person or organization responsible for handling the referral
- if the Task is being transmitted via messaging, the referenced PractitionerRole resource SHALL be included in the message as a
Bundle.entry
.output (for further discussion)
- MAY to used to provide the outcome of a ServiceRequest
.output.valueReference (for further discussion)
- a reference to Communication (or potentially other resources)
- if the Task is being transmitted via messaging, the referenced FHIR resource SHALL be included in the message as a
Bundle.entry