Messaging
The Alberta eReferral-eConsult Messaging Interoperability Specification, enables a bi-directional exchange of information about referral requests, appointments, referral related tasks and communications between two trusted systems using FHIR messaging, and is the basis of integrations that connect systems participating in eReferral-eConsult related exchanges to one another.
In FHIR messaging, a message is sent from a source application to a destination application when an event happens. A message is a Bundle resource of type message, that conforms to specific rules.
The Alberta eReferral-eConsult messaging implementation follows synchronous Message Request and Response paradigm using HTTP-based (POST) MessageHeader/$process-message FHIR operation.
The Alberta eReferral-eConsult REST-based service has two key interfaces:
- A Community Information Integration (CII) inbound AB:eReC FHIR interface that allows EMRs to submit (POST) FHIR referral messages intended to be lodged within the provincial Electronic Referral Solution (ERS).
- A client-side AB:eReC FHIR interface that allows for CII to POST referral notifications and updates from the ERS to an EMR.
Refer to a separate document: CII eReferral Inbound Interface - Web Service API for further details.
See section on Constructing Messages and Reducing Message Size in Guidance for additional guidance.
Transactions
The following table shows the transactions that are used in this specification. This is arranged in order of the transaction id.
| ID | Name | Focus | Event Code |
|---|---|---|---|
| eReCm-1 | Send new service request | ServiceRequest | add-service-request |
| eReCm-2 | Notify new service record | ServiceRequest | notify-add-service-record |
| eReCm-3 | Notify update service request | ServiceRequest | notify-update-service-request |
| eReCm-5 | Revoke service request | ServiceRequest | revoke-service-request |
| eReCm-6 | Notify new request processing | Task | notify-add-process-request |
| eReCm-7 | Notify update request processing | Appointment; Task | notify-update-process-request |
| eReCm-8 | Notify new appointment | Appointment | notify-add-appointment |
| eReCm-9 | Send communication from requester | Communication | send-communication-from-requester |
| eReCm-10 | Send communication from performer | Communication | send-communication-from-provider |
| eReCm-11 | Notify update service record | Appointment; ServiceRequest | notify-update-service-record |
Transactions by Participants
The following tables shows the outgoing and incoming transactions that are expected to be supported by each participant.
See Participants for more information
Requester HCP (Source System)
| Incoming / Outgoing | Transaction ID | Transaction Name | Scope |
|---|---|---|---|
| Outgoing | eReCm-1 | Send new service request | Phase 1 |
| Outgoing | eReCm-3 | Notify update service request | Future |
| Outgoing | eReCm-5 | Revoke service request | Future |
| Outgoing | eReCm-9 | Send communication from requester | Future |
| Incoming | eReCm-2 | Notify new service record | Phase 1 |
| Incoming | eReCm-6 | Notify new request processing | Phase 1 |
| Incoming | eReCm-7 | Notify update request processing | Future |
| Incoming | eReCm-10 | Send communication from performer | Future |
| Incoming | eReCm-11 | Notify update service record | Future |
Central Access & Triage (CAT) (Central System)
| Incoming / Outgoing | Transaction ID | Transaction Name | Scope |
|---|---|---|---|
| Incoming | eReCm-1 | Send new service request | Phase 1 |
| Incoming | eReCm-3 | Notify update service request | Future |
| Incoming | eReCm-5 | Revoke service request | Future |
| Incoming | eReCm-6 | Notify new request processing | Future |
| Incoming | eReCm-7 | Notify update request processing | Future |
| Incoming | eReCm-8 | Notify new appointment | Future |
| Incoming | eReCm-9 | Send communication from requester | Future |
| Incoming | eReCm-10 | Send communication from performer | Future |
| Outgoing | eReCm-1 | Send new service request | Future |
| Outgoing | eReCm-2 | Notify new service record | Phase 1 |
| Outgoing | eReCm-3 | Notify update service request | Future |
| Outgoing | eReCm-5 | Revoke service request | Future |
| Outgoing | eReCm-6 | Notify new request processing | Phase 1 |
| Outgoing | eReCm-7 | Notify update request processing | Future |
| Outgoing | eReCm-9 | Send communication from requester | Future |
| Outgoing | eReCm-10 | Send communication from performer | Future |
| Outgoing | eReCm-11 | Notify update service record | Future |
Performer HCP) (Target System)
| Incoming / Outgoing | Transaction ID | Transaction Name | Scope |
|---|---|---|---|
| Incoming | eReCm-1 | Send new service request | Future |
| Incoming | eReCm-3 | Notify update service request | Future |
| Incoming | eReCm-5 | Revoke service request | Future |
| Incoming | eReCm-9 | Send communication from requester | Future |
| Outgoing | eReCm-6 | Notify new request processing | Future |
| Outgoing | eReCm-7 | Notify update request processing | Future |
| Outgoing | eReCm-8 | Notify new appointment | Future |
| Outgoing | eReCm-10 | Send communication from performer | Future |