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. Technical Context
    3. Messaging
    4. Actors and Transactions

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

Actors and Transactions

Requester/Performer Integration

The following diagrams illustrate the actors and transactions between the eReC Requester and eReC Performer actors, in scope for the CA:eReC Messaging Interoperability Specification.

eReC-Transactions

Informer/Recipient Integration

The following diagrams illustrate the actors and transactions between the eReC Informer and eReC Recipient actors, in scope for the CA:eReC Messaging Interoperability Specification.

eReC-Transactions-InterestedParty

Messaging Compliance

The table below lists the transactions for each actor directly involved in CA:eReC Messaging.

To claim compliance with CA:eReC Messaging, an actor SHALL:

  • support all transactions corresponding to the Maturity Level being claimed and lower, and
  • appropriately handle error messages generated by less mature solutions that are unable to process messages sent.

Solutions MAY support a subset of transactions generally associated with solutions of higher maturity levels.

In other words:

  • An actor conforming to Maturity Level 3 SHALL implement transactions from Maturity Level 3, Maturity Level 2 and Maturity Level 1
  • An actor conforming to Maturity Level 2 SHALL implement transactions from Maturity Level 2 and Maturity Level 1 and MAY implement transactions from Maturity Level 3
  • An actor conforming to Maturity Level 1 SHALL implement transactions from Maturity Level 1 and MAY implement transactions from Maturity Level 2 and Maturity Level 3
Actor Transaction Event Code Direction Maturity Level
eReC Requester1 Send new service request [eReCm-1] add-service-request Outgoing L1
Notify update service request [eReCm-3] notify-update-service-request Outgoing L2
Notify data correction [eReCm-4] notify-data-correction Incoming L2
Revoke service request [eReCm-5] revoke-service-request Outgoing L1
Notify new request processing [eReCm-6] notify-add-process-request Incoming L2
Notify update request processing [eReCm-7] notify-update-process-request Incoming L2
Notify new appointment [eReCm-8] notify-add-appointment Incoming L3
Send communication from requester [eReCm-9] send-communication-from-requester Outgoing L3
Send communication from performer [eReCm-10] send-communication-from-provider Incoming L3
eReC Performer2 Send new service request [eReCm-1] add-service-request Incoming L1
Notify update service request [eReCm-3] notify-update-service-request Incoming L2
Notify data correction [eReCm-4] notify-data-correction Outgoing L2
Revoke service request [eReCm-5] revoke-service-request Incoming L1
Notify new request processing [eReCm-6] notify-add-process-request Outgoing L2
Notify update request processing [eReCm-7] notify-update-process-request Outgoing L2
Notify new appointment [eReCm-8] notify-add-appointment Outgoing L3
Send communication from requester [eReCm-9] send-communication-from-requester Incoming L3
Send communication from performer [eReCm-10] send-communication-from-provider Outgoing L3
eReC Informer 2 Notify new service record [eReCm-2] notify-add-service-record Outgoing L3
Notify update service record [eReCm-11] notify-update-service-record Outgoing L3
eReC Recipient 1 Notify new service record [eReCm-2] notify-add-service-record Incoming L3
Notify update service record [eReCm-11] notify-update-service-record Incoming L3

1 Vendors claiming Level 3 compliance for the eReC Requester SHOULD demonstrate the actor's use with a compliant eReC Recipient (link).

2 Vendors claiming Level 3 compliance for the eReC Performer SHOULD demonstrate the actor's use with a compliant eReC Informer (link).

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