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 - ServiceRequest (CA:eReC)
This bundle provides instructions on serviceRequests can be sent as part of an eReferral.
MessageDefinition
A ServiceRequest SHALL be the focus of messages corresponding to the following events:
| Event | Category | Purpose | Allowed Responses | Response Situation |
|---|---|---|---|---|
| add-service-request | consequence | To request that a ServiceRequest created on the eReC Source be performed on an eReC Target. | notify-add-process-request | When the request is successfully processed, a 'process-request' Task with status SHALL be returned to the requester. |
| notify-add-service-request | notification | To notify systems other than the eReC Target that a new ServiceRequest has been created. | ||
| revoke-service-request | consequence | To request that all information related to a ServiceRequest terminated on the eReC Source be removed. | notify-update-process-request | When the request has been successfully processed, a 'process-request' Task with status 'cancelled' SHOULD be returned to the requester. |
| notify-update-service-request | notification | To notify systems that a ServiceRequest or its status has been updated. | ||
| notify-data-correction | notification | To notify systems that information in a ServiceRequest or related resource has been corrected on the eReC Target. | notify-update-servicerequest | When the request is successfully processed, any update to the ServiceRequest or status MAY be sent to the performer. |
Message Bundle: ServiceRequest
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
- the ServiceRequest(s) referenced in
MessageHeader.focus - 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 - references to other
ServiceRequest.supportingInfowhere needed
ServiceRequest Bundles MAY contain multiple ServiceRequests
Note:
To enable conformance testing against the requirements of this IG, the requirements summarized above are formally specified as constraints 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.