FHIR Artifacts > MessageDefinition: Communication Bundle
Communication Bundle
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 RMS Source to RMS Target. | send-communication-from-provider | The RMS Target has received the message and resonds with a Communication |
| send-communication-from-provider | consequence | To send a question or additional information about a ServiceRequest from RMS Target to RMS Source. | send-communication-from-requester | The RMS Source has received the message and responds with a Communication |
| add-communication | consequence | To send a question or additional information about a ServiceRequest to a system other than an RMS Source and Target | add-communication |
Message Bundle: Communication
Description
Entries in the message Bundle for these business events will be determined by the content of the ServiceRequest which, minimally, SHALL include:
- a MessageHeader
- a Communication referenced in
MessageHeader.focus - the ServiceRequest(s) the Communication is based on (Communication.basedOn)
- the Patient who is the subject of the ServiceRequest (
ServiceRequest.subject) - PractitionerRole(s) referenced in
MessageHeader.author,ServiceRequest.requester, the requestedServiceRequest.performerwhere, each SHALL reference an Organization, Location and/or Practitioner
The message SHOULD also include references to the Patient who is the Communication.subject, the PractitionerRole of the Communication.sender and any other Communication it was created in response to (Communication.inResponseTo). It MAY also include references to other ServiceRequest.supportingInfo sent by the Source.
Note:
To enable conformance testing against the requirements of this IG, the requirements summarized above are formally specified as contraints within FHIR artifacts published in this IG. Implementers are strongly encouraged to become familiar with these formal specifications and to rely on them as the source of truth.
Information about how implementers can validate message instances is provided on the downloads page of this IG.