Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) v1.1.0-DFT-Ballot

1.1.0-DFT-Ballot   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
    • 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

preBallot - The specification is currently in ballot review 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 RFI related to a Service Request received Target System Communication (CA:eReC) n/a send-communication-from-provider Source System Notify Requester HCP that a request has been received requiring a response
Requester HCP Sends response to RFI from Source System Source System Communication (CA:eReC) n/a send-communication-from-requester Target System Notify Performer HCP that there is a response to the RFI they sent

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.

Communications Payload

In communication messages the Communication resource SHALL contain:

  • payload.contentString containing a question or comment as text
  • category is a coded element typically containing rfi (request for information) or gen (general communication)
  • basedOn, sender, subject containing references to the ServiceRequest, PractitionerRole sending the Communication and Patient respectively

Responses

When responding to a communication received, the Communication will also contain:

  • inResponseTo referencing the Communication received
  • payload.contentString containing a text response, and/or
  • one or more payload.contentAttachment containing a .url to retrieve an attachment or .data

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