Visit the HL7 website
Visit the FHIR website

Pan-Canadian FHIR Exchange (CA:FeX) IGuide 2.2.0 DFT-Ballot

2.2.0-DFT-Ballot   Canada flag
  • Home
  • Business Context
    • Project Background
    • Scope
    • Relationship to Other Specifications
    • Use Cases
  • Technical Context
    • Overview
    • FHIR Exchange Paradigms
    • Sequence Diagrams
    • Actor Mapping to Interoperability Specification
    • Security
  • Actor and Conformance Options
    • Technical Actors
    • Actor Options
    • Conformance Requirements
  • FHIR Artifacts
    • Profiles and Extensions
    • Search Parameters
    • Operations
    • Capability Statements
  • Change Log
    • Change Log
    1. Home
    2. Technical Context
    3. Actor Mapping to Interoperability Specification

DFT Ballot - This specification is currently in ballot review and subject to change. It is not ready for limited roll-out or production level use. For a full list of available versions, see the Directory of published versions

Actor Mapping to Interoperability Specification

This section provides implementation recommendations for actors and services involved in the CA:FeX transactions. The Interoperability Recommendations tables outline how system actors (e.g., Data Consumer, Data Responder) participate in supported services and the technical profiles or transactions that enable those interactions.

These tables serve as a tabular representation of the corresponding sequence diagrams and include added details to support implementers in understanding integration points, profiles, and service patterns within their implementation context.

Each table is based on the corresponding use case flow diagrams and sequence diagrams presented in this guide:

  • Use Cases illustrate the clinical context and information flow.
  • Sequence Diagrams translate that flow into technical interactions.
  • Interoperability Recommendations Tables summarize the technical roles, services, and applicable profiles or transactions described in those diagrams.

Each row represents a specific actor (e.g., Data Consumer, Data Responder) and outlines:

  • The service(s) they support in each use case
  • The technical actor role they play
  • The profile or standard used (e.g., CA:FeX, PDQm, PMIR)
  • Where applicable, the interoperability transaction or capability that supports the service
Interoperability Recommendations Sequence Diagram Related Use Case
Table 1 – Interoperability Recommendations for Use Case 1: Create and Submit Document UC-01-sequence-diagram UC-01 Create and Submit Document
Table 2 – Interoperability Recommendations for Use Case 2: Query and Retrieve Document UC-02-sequence-diagram UC-02 Query and Retrieve Document
Table 3 – Interoperability Recommendations for Use Case 3: Create and Submit Data UC-03-sequence-diagram UC-03 Create and Submit Data
Table 4 – Interoperability Recommendations for Use Case 4: Query and Retrieve Data UC-04-sequence-diagram UC-04 Query and Retrieve Data
Table 5 – Interoperability Recommendations for Use Case 5: Fetch Document References UC-05-sequence-diagram UC-05 Fetch Document References

The Implementation Expectation column uses the terms:

  • Expected
    Represents interactions or services that are expected to be part of CA:FeX-aligned workflows. These steps reflect baseline implementation patterns but are not prescriptive or enforced as strict requirements.

  • Optional
    Represents interactions or services that may be implemented depending on jurisdictional policies, system capabilities, or implementation context. These steps support flexibility within CA:FeX workflows but are not universally expected.

Table of Contents | IG © based on FHIR R4 | Package package:ca.infoway.io.cafex@2.2.0-DFT-Ballot | Version History
HL7® and FHIR® are the registered trademarks of Health Level Seven International