Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC)

1.1.0-DFT   Canada flag
  • Index
  • Home
  • Business Context
    • Business Models
    • Use Cases
    • Business Events
    • Business Rules
    • Privacy and Security Guidance
    • Provincial Considerations
  • Technical Context
    • Technical Foundation
    • Integration Patterns
    • Messaging
    • Sequence Diagrams
    • Conformance Requirements
  • FHIR Artifacts
    • Messaging Events
    • Resource Profiles
    • Extensions
    • Terminology
    • Identifier Naming System
    • Examples
    • Capability Statements
    • Downloads
    • ---
    • Appointment (CA:eReC)
    • Bundle (CA:eReC)
    • Communication (CA:eReC)
    • DocumentReference (CA:eReC)
    • Location (CA:eReC)
    • MessageHeader (CA:eReC)
    • Organization (CA:eReC)
    • Patient (CA:eReC)
    • Practitioner (CA:eReC)
    • PractitionerRole (CA:eReC)
    • HealthcareService (CA:eReC)
    • QuestionnaireResponse (CA:eReC)
    • ServiceRequest (CA:eReC)
    • Task (CA:eReC)
  • Change Log
    1. Index
    2. Business Context
    3. Business Events
    4. L3: Communications

DFT - The specification is currently in development and subject to change. For a full list of available versions, see the Directory of published versions

L3: Communications

Secure communications between health care providers related to eReferral or eConsult are supported by messages that focus on the Communication resource.

The messaging supports both "general communications" and "requests for information" (RFI). In practice, they are usually the latter and therefore should be treated as consequence events.

Trigger Events & Interactions

Party Action / Trigger Sending System Focus of Message State Change Event Code Receiving System Expected action upon receipt of message
Performer HCP Sends a communication related to a received Service Request Target System Communication (CA:eReC) n/a send-communication-from-provider (L3) Source System Notify Requester HCP that a communication has been received that may require a response
Requester HCP Sends a communication from Source System Source System Communication (CA:eReC) n/a send-communication-from-requester (L3) Target System Notify Performer HCP that there is a communication that may be a response

Requests for Information (RFI)

A request for information or RFI is to communicate that a service request received is not complete. In many cases, the Performer HCP will either have not accepted the request or will have placed it on hold pending a response.

General Communications

A general communication is used to pass information to the performer or requester, there is no requirement to respond or to place the referral on hold.

Single Entry Models

Where referrals are routed or split, Central Systems may be required to transmit Requests for Information received from Target Systems back to the Source System / Requester HCP.

Party Action / Trigger Sending System Focus of Message State Change Event Code Receiving System Expected action upon receipt of message
Central System Receives a communication from a Target System Central System Communication (CA:eReC) n/a send-communication-from-provider (L3) Source System Notify Requester HCP
Central System Receives a communication from a Source System Central System Communication (CA:eReC) n/a send-communication-from-requester (L3) Target System Notify Performer HCP

Note: Secure communications are an L3 level capability with implications for patient care. Central Systems that integrate with less mature Source Systems must have appropriate processes in place to either restrict or support electronic communications with Target Systems.


IG © based on FHIR R4 | Package package:ca.infoway.io.erec@1.1.0-dft
HL7® and FHIR® are the registered trademarks of Health Level Seven International