Visit the HL7 website
Visit the FHIR website

Pan-Canadian eReferral-eConsult (CA:eReC) CIBuild

current   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

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

Integration Patterns

This page provides an overview of integration patterns supported by Messaging where the objective is to provide implementable technical specifications that support real-world architectures that support a range of different Business Models.

The integration patterns on this page illustrate how four reusable technical actors can be assembled to support several different real-world architectures.

Integration Patterns Section Description
Technical Actors CA:eReC Messaging defines four different Technical Actors that perform different roles within messaging integrations.
Basic Integration Patterns CA:eReC Messaging is meant to provide implementable technical specifications in support of real-world architectures associated with a range of integration patterns supporting different business models. Two basic message integration patterns provide building blocks for real-world solutions.
Example Architectures Real-world solutions may build upon the basic integrations to provide more functional solutions for users. Below are illustrations of potential implementations that could serve as stand-alone solutions or be composed into larger networks.
Actor Options Options are provided for each actor related to the capability level they support.
Actor Groupings Grouped Actors are actors which are implemented together on a single system to provide more complex functionalities.

Table of Contents | IG © based on FHIR R4 | Package project:CA-eReC | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International