...
- 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.23-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 Messaging section (CA:eReC v1.0.2 3 DFT) of the pan-Canadian.
Testing the Secure, Exchange Transactions
...
The test cases 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. FHIR message format and content are validated for each transaction. 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 | |||
By IG | IG Description and Purpose of Test Cases | Integration Profiles and Actors Involved | Test Case Peer Type & Supporting Tools* |
CA:eReC | The Projectathon 2025 will focus on interoperability demonstrations based on the pan-Canadian eReferral/eConsult Interoperability Specification (CA:eReC v1.0.23-DFT) Interoperability Specification. The CA:eReC specification defines the building blocks to create, send and receive eReferrals/eConsults. The purpose of testing CA:eReC is to ensure systems have the ability to create, send and receive FHIR messages (e.g., ServiceRequestsServiceRequest MessageBundles) over the internet. These test cases will also ensure that the eReferrals are formatted and contain 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 CA:eReC, go here. |
| No-Peer (Gazelle platform, FHIR Validator, CA:eReC Simulators) Peer-to-Peer (Gazelle platform, FHIR Validator) |
ON eReC | The Ontario eReferral/eConsult FHIR Implementation guide v0.12.0 Draft uses CA:eReC as the FHIR resource profile baseline and was developed in collaboration with the FHIR Implementers community, solution vendors and Canada Health Infoway. The specification has an open review in progress and potential for changes is possible until March 2025. These test cases will ensure that eReferrals contain the additional required message content, valuesets and bindings according to the ON eReC implementation guide. An ON 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 ON eReC, go here. |
| No-Peer (Gazelle platform, FHIR Validator, CA:eReC Simulators) Peer-to-Peer (Gazelle platform, FHIR Validator) |
...