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 Groupings

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 Groupings

Grouped Actors are actors which are implemented together on a single system to provide more complex functionalities. For a grouping to occur, an actor from this profile (Column 1 - eReC Actor) shall implement all the required transactions and/or content modules in this profile in addition to all the transactions required for the grouped actor (Column 2 - Actor to be grouped with).

eReC Actor Actor to be grouped with Optionality of grouping Notes
eReC Requester eReC Informer Optional Grouping an eReC Informer with an eReC Requester on a system provides the ability for the system to send a copy of a service record sent to an eReC Performer system as well as updates made in response to information received from an eReC Performer system to be shared with other interested parties and/or other systems used by a Requester HCP. See system integrations with local point of service systems (POS) under the Point to Point Model
eReC Performer eReC Informer Optional Grouping an eReC Informer with an eReC Performer on a system provides the ability for the system to send a copy of a service record created or updated in response to information received from an eReC Requester to be shared with other interested parties and/or other systems used by a Performer HCP. See system integrations with local point of service systems (POS) under the Point to Point Model.
eReC Performer eReC Requester Optional In systems used to support Central Intake and Central Access & Triage business models, the eReC Requester may need to transmit service requests that have been created or reassigned by the Central Intake or CAT team to a Performer HCP(s) who work on another system(s).
eReC Performer eReC Informer (Link) Optional In systems used to support Central Intake and Central Access & Triage business models, the eReC Informer (link) may be implemented to share information about and updates to service requests that have been created or reassigned by the Central Intake or CAT teams to a Requester HCP(s) that work on another system(s). The Link option relates to the ability for the system to associate service requests received by the eReC Performer with new requests created and managed within the system in messages sent by the eReC Informer. See: L3: Advanced Workflows
eReC Requester eReC Recipient (Link) Optional Where Example: Central Intake in Point to Point and Central Access & Triage business models are in use, implementing an eReC Recipient (Link) with the eReC Requester on the system used by the Requester HCP provides a mechanism for the system to receive information about and updates to a service request that has been created or reassigned by the Central Intake or CAT teams. The Link option relates to the ability for the system to associate service requests received by the eReC Recipient with existing requests created and managed within the system. See: L3: Advanced Workflows

Where this grouping exists, the system may receive two streams of updates related to a request sent from the system used by the Central Intake or CAT team:
- eReC Requester: will receive FHIR messages that provide notifications focused on services (Tasks) performed by the organization operating Central Intake or CAT with the purpose of conveying acceptance, completion, etc of the parent request received from the Requester HCP / eReC Requester.
- eReC Recipient: will receives notifications to update the service record created and managed on the system used by the Central Intake or CAT team with the purpose of passing along information about downstream services requested (child requests) created by Central Intake or CAT and performed by the Performer HCP.

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