CA:eReC Test Cases: Projectathon 2025

Welcome to the Projectathon 2025 test case information page!

On this page, you will find:

CA:eReC Testing Approach

The 2025 Projectathon is dedicated to supporting eReferral implementation projects across Canada. Testing will focus on validating that the vendor systems have the capabilities needed to securely exchange well-formed eReferral information with other systems. Vendors will have an opportunity to test and demonstrate these capabilities in two facets of the CA:eReC specification:

CA:eReC Exchange transactions - ensuring that the system(s) can securely exchange eReferral messages using the recommended FHIR messaging exchange methods as presented in the Messaging section.
CA:eReC Message format and content – ensuring that eReferral messages are structured in the expected format and that it contains the required information using the correct data types and valuesets, where specific valuesets are defined as required in the pan-Canadian eReferral-eConsult specifications (CA:eReC v1.0.2-DFT).

1. CA:eReC Exchange Transactions

This area of testing will focus on validating the recommended exchange methods of eReferral FHIR messages as presented in the Reference Architecture (RA v0.2.0 DFT-Ballot), referenced by the PS-CA and CA:FeX specifications. Under ideal conditions, depending on the number of participating vendors and their system capabilities, tests will offer a high degree of coverage for all profiles.

Testing the Secure, Exchange Transactions

Testing supports for the Patient Summary secure, exchange transactions will be provided using a combination of test cases and tools (see Table Test Cases for Secure, Exchange Transactions below for more information).

2. CA:eReC Message Format and Content

Test cases are focused on ensuring that eReferral messages are structured in the expected format and that it contains the required information using the correct data types and valuesets, where specific valuesets are defined as required in CA:eReC.

In addition to testing the PS-CA, test cases will validate the harmonized provincial eReferral specifications from Ontario (ON eReC) which are very closely aligned to the CA:eReC. All should be supported by minimal configuration of capability in the vendor systems. The test cases will ensure that the Patient Summary is formatted and contains the required content according to the respective Jurisdiction Implementation Guide (IG), where applicable. Vendors will need to prepare to validate PT data against both CA:eReC and PT Implementation Guides.

The test cases will highlight where configuration is needed and test that the configuration is applied properly, based on claimed vendor conformance.

Testing the Document Format and Content

Testing supports for the Patient Summary document format and content validation will be provided using a combination of test cases, test data sets, and tools (see table Test Cases for Document Format and Content below for more information). While test cases reside in Gazelle, they may refer to data sets which will be available on the Test Data Sets page. The data sets will be available in an Excel spreadsheet format.

Test Cases Overview

The purpose of this overview is to provide an understanding of:

What will be tested:
- integration profiles included in the test cases
- descriptions and purpose of test cases
- actors and transactions involved in the test cases
- types of test cases and supporting tools
Where to find the test cases
When to run the test cases

What will be Tested (Implementation Guides)

The following table describes Implementation Guides being tested, purpose of each, profiles involved and types of tests and supporting tools. To learn more about the IHE Profiles, be sure to watch the information videos included in the Description sections.

Test Cases for Document Format and Content
By IG	IG Description and Purpose of Test Cases	IHE Profiles Involved	Test Case Peer Type & Supporting Tools*
CA:eReC	The Projectathon 2025 will focus on interoperability demonstrations based on the pan-Canadian Patient Summary (PS-CA v2.0.0 DFT-Ballot). The CA:eReC specification defines the building blocks to create, send and receive eReferrals/eConsults. The purpose of these test cases will ensure that the eReferrals are formatted and contains the required content according to the CA:eReC Implementation Guide. A CA:eReC clinical data set will be provided to support these test cases. Refer to the Test Data Sets for more details. To read more about the PS-CA, go here.	CA:eReC	No-Peer (Gazelle platform, FHIR Validator, CA:eReC Simulators) Peer-to-Peer (Gazelle platform, FHIR Validator)
ON eReC	The Ontario Patient Summary is based on the International Patient Summary standard and was developed in collaboration with Canada Health Infoway and other jurisdictions and with preliminary input from primary care clinicians and solution vendors. The Ontario Patient Summary (PS-ON) Standard aligns, where applicable, to the International Patient Summary (IPS) HL7 FHIR standard, the Pan-Canadian Patient Summary (PS-CA) Standard (under concurrent development), and the Canadian Baseline (CA-Baseline). To read more about the PS-ON, go here.	CA:eReC	No-Peer (Gazelle platform, FHIR Validator, CA:eReC Simulators) Peer-to-Peer (Gazelle platform, FHIR Validator)

*To learn more about the Supporting Tools, go here.

The table below describes the integration profiles being tested, purpose of each, actors involved and types of tests and supporting tools.

The Test Cases for Secure Exchange Transactions are designed to validate the interoperability capabilities of the system under test in exchanging eReferrals. Each test case typically defines a specific transaction or action that must be validated between two systems or actors. It includes detailed prerequisites, expected disruptions, involved actors, step-by-step instructions, and any supporting tools required for testing. To explore and execute these test cases, please access Gazelle, where you can find the full set of test cases categorized by interoperability profile, actor, and transaction.

Test Cases for Secure, Exchange Transactions
By Interoperability Profile	Profile Description and Purpose of Test Cases	Actors Involved	Test Case Peer Type & Supporting Tools*
CA:eReC	The pan-Canadian FHIR Exchange (CA:FeX) is an implementable, testable interoperability specification based on HL7 FHIR Implementation Guides, that defines building blocks to enable creating, consuming and sharing clinical data via FHIR RESTful exchange patterns. The purpose of testing CA:eReC is to ensure systems have the ability to create, send and receive FHIR messages (e.g., ServiceRequests) over the internet. To read more technical information about CA:FeX, go here.	eReC Requester eReC Performer	No-Peer (CA:eReC Client & Server Simulator) Peer-to-Peer (Gazelle platform)