DRAFT - The specification is currently in development and subject to significant change. It is not ready for limited roll-out or production level use.
MessageBundle - Task (CA:eReC)
MessageDefinition
A Task SHALL be the focus of messages corresponding to the following events:
| Event | Category | Purpose | Allowed Responses | Response Situation |
|---|---|---|---|---|
| notify-add-process-request1 | notification | To notify systems that an eReC Target has created a Task for a user to perform a ServiceRequest. | ||
| notify-update-process-request1,2 | notification | To notify systems that work has been performed in response to a ServiceRequest and that the Task, its status or related information has changed. |
1 'perform-request' Tasks are identified with Task.code 'perform-request'
2 in cases where discreet events are not defined in this IG, implementers SHOULD use the notify-update-process-request event to share information about actions the Performer has planned or taken in response to the ServiceRequest. In these cases, a message MAY include more than one MessageHeader.focus to convey information about both the 'process-request' Task's status and any additional resource(s) added or updated.
Message Bundle: Task
Description
Entries in the message Bundle for these business events will be determined by the content of the ServiceRequest the Task is based on which, minimally, SHALL include:
- a MessageHeader
- a Task referenced in
MessageHeader.focus - PractitionerRole(s) referenced in
MessageHeader.authorSHALL reference an Organization, Location, and/or Practitioner
The ServiceRequest the Task is based on SHALL either be referenced or included in the Bundle. If it is included in the Bundle, then the Bundle SHALL include:
- the Patient who is the subject of the ServiceRequest (
ServiceRequest.subject) - PractitionerRole(s) referenced in
ServiceRequest.requesterand the requestedServiceRequest.performerwhere each SHALL reference an Organization, Location, and/or Practitioner
Note:
To enable conformance testing against the requirements of this IG, the requirements above are formally specified within the FHIR artifacts published in this IG. Implementers are strongly encouraged to become familiar with these formal specifications and rely on them as the source of truth.