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 Requester be performed on an eReC Performer. 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-record notification To notify eReC Recipient systems that a new Service Record has been created.
notify-update-service-record notification To notify eReC Recipient systems that an existing Service Record has been updated.
revoke-service-request consequence To request that all information related to a ServiceRequest terminated on the eReC Requester 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 Performer. notify-update-service-request When the request is successfully processed, any update to the ServiceRequest or status MAY be sent to the performer.

Message Bundle: ServiceRequest

ServiceRequest Message Bundle

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 requested ServiceRequest.performer where, each SHALL reference an Organization, Location, and/or Practitioner
  • references to other ServiceRequest.supportingInfo where 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 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.