Pan-Canadian eReferral-eConsult (CA:eReC)
1.1.0-DFT 
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 - Communication (CA:eReC)
MessageDefinition
A Communication resource SHALL be the focus of messages corresponding to the following events:
| Event | Category | Purpose | Allowed Responses | Response Situation |
|---|---|---|---|---|
| send-communication-from-requester | consequence | To send a question or additional information about a ServiceRequest from eReC Requester to eReC Performer. | ||
| send-communication-from-provider | consequence | To send a question or additional information about a ServiceRequest from eReC Performer to eReC Requester. |
Message Bundle: Communication
Description
Entries in the message Bundle for these business events will be determined by the content of the ServiceRequest the Communication is based on which, minimally, SHALL include:
- a MessageHeader
- a Communication referenced in
MessageHeader.focus - PractitionerRole(s) referenced in
MessageHeader.authorSHALL reference an Organization, Location, and/or Practitioner
The ServiceRequest the Communication 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 ServiceRequest.performercould reference either a PractitionerRole or HealthcareService resource
In addition to the above, a response to a previously received communication SHOULD also include the Communication.id from the Communication being responded to, referenced in Communication.inResponseTo as a bundle entry
Note:
To enable conformance testing against the requirements of this IG, the requirements summarized above are formally specified as constraints within Resource Profiles in this IG. Implementers are strongly encouraged to become familiar with these formal specifications and to rely on them as the source of truth.