DFT - The specification is currently in development and subject to change. For a full list of available versions, see the Directory of published versions

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.
notify-update-service-record1,2	notification	To notify eReC Recipient systems that an existing Service Record has been updated when there is updated information or status as work related to the downstream ServiceRequest is performed or completed.

¹ 'process-request' Tasks are identified with Task.code 'process-request'

² in cases where discrete 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.author SHALL reference an Organization, Location, and/or Practitioner

• This Task will either be assigned to a:
  • A health care provider (HCP) in a PractitionerRole. In these cases, the eReC Performer on the Target System SHOULD send event based messages in response to actions taken with:
  • the assigned PractitionerRole in Task.owner
  • the PractitionerRole responsible for the action that generated the message in MessageHeader.author
• A central intake service or similar entity performing a clerical function supporting a single entry model. In these cases, the eReC Performer on a Central System MAY send event based messages in response to actions taken with:
  • the HealthcareService performing the clerical function Task.owner
  • MessageHeader.author unpopulated.

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.requester and the requested ServiceRequest.performer where each SHALL reference an Organization, Location, and/or Practitioner
• ServiceRequest.performer could reference either a PractitionerRole or HealthcareService resource

Note:

To enable conformance testing against the requirements of this IG, the requirements above are formally specified within the Resource Profiles published in this IG. Implementers are strongly encouraged to become familiar with these formal specifications and rely on them as the source of truth.