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. Integration Patterns
    4. Actor Options

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


Actor Options

The table below lists the options that may be selected for each actor. Dependencies between options when applicable are specified in notes.

If no option is specified, the default capabilities are required for that actor. Otherwise, the capabilities for the specific option are required.

Actor Option Name Notes
eReC Requester L1
L2
L3 (default)
Note 1
eReC Performer L1
L2
L3 (default)
Note 1
eReC Informer None (default)
Link
Note 2
eReC Recipient None (default)
Link
Note 3

Note 1:

L1, L2, L3 Options represent the maturity level of the Actor. Most procurements will require L3 support. To function in real-world environments, L2 and L3 systems SHOULD be designed to safely integrate with less mature systems.

Note 2:

The Link Option is part of more complex flows, typically involving a Central System. eReC Informers that support the Link option are able to associate service requests / service records created and managed in the system with a service request received by eReC Performer actor when sending messages. See: Routing Splitting Chaining

Note 3:

The Link Option is part of more complex flows, typically involving a Central System. eReC Recipients that support the Link option are able to associate service requests / service records created and managed in the Central System with the service request sent by eReC Requester actor when receiving messages. See: Routing Splitting Chaining

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