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

DFT - The specification is currently in development 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)
L1, L2, L3 Options represent Actor Maturity Levels.
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.
eReC Performer L1
L2
L3(default)
L1, L2, L3 Options represent Actor Maturity Levels.
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.
eReC Informer None(default)
Link
The Link Option is used to enable more complex flows, typically involving a Central System.
eReC Informers that support the Link option SHALL be able to use FHIR messaging to notify a Source System that a child service request / service record was created within the RMS System in response to the parent service request received by the eReC Performer actor.
See: Routing, Splitting and Chaining for more information.
eReC Recipient None(default)
Link
The Link Option is used to enable more complex flows, typically involving a Central System.
eReC Recipients that support the Link option SHALL be able to use FHIR messaging to associate a child service request / service record received from another RMS with the parent service request initially sent by eReC Requester actor.
See: Routing, Splitting and Chaining for more information.

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