...
In addition to testing the PS-CA, test cases will validate the harmonized provincial Patient Summary specifications from British Columbia Ontario (PS-CA:BC), Ontario ON) and Alberta (PS-ON), AB) which are very closely aligned to the PS-CA, and from New Brunswick (PS-CA:NB) and , Alberta British Columbia (PS-ABCA:BC) which are very closely aligned to which have adopted the PS-CA and FHIR profiles. All should be supported by minimal configuration of capability in the vendor systems. The test cases will will ensure that the Patient Summary is formatted and contains the required content according to the respective Jurisdiction Implementation Guide (IG).
The test cases will highlight where configuration is needed and test that the configuration is applied properly, based on claimed vendor conformance.
, where applicable. Vendors will need to prepare to validate PT data against both PS-CA and the applicable PT Implementation Guide. Refer to the Test Cases for Document Format and Content table below for details about each PT implementation guide.
The test cases will highlight where configuration is needed and test that the configuration is applied properly, based on claimed vendor conformanceThe Projectathon will offer an assessment of the Patient Summary document against the PS-CA:BC, PS-ON, PS-CA:NB and PS-AB implementation guidance as represented in the respective specifications, in addition to the PS-CA. Patient Summary documents will be validated against PS-CA and also, validated against Jurisdiction implementation guide. Vendors will need to prepare to validate PT data against both PS-CA and PT Implementation Guides.
Testing the Document Format and Content
...
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* | ||
PS-CA | The Projectathon 2025 will focus on interoperability demonstrations based on the pan-Canadian Patient Summary (PS-CA v2.0.0 DFT-Ballot) and the associated pan-Canadian FHIR Exchange (CA:FeX v2.1.0 DFT-Ballot) specifications. The PS-CA specification defines the building blocks to create and share patient summaries. The purpose of the test cases for the PS-CA will ensure that the Patient Summary is formatted and contains the required content according to the PS-CA Implementation Guide. A PS-CA 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. |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform) | ||
PS-CA:BC | The PS-CA: BC Patient Summary Project has been endorsed by Canada Health Infoway and BC Provincial Digital Health as a key strategy to support patient information sharing across care settings. PS-CA: BC Implementation Guide leverages foundational artifacts from PS-CA, including BC-specific guidance tailored to provincial healthcare needs. For Release 1, national artifacts are utilized, with the potential to build on PS-CA profiles for BC-specific needs in future releases. Since the PS-CA is based on the IPS, provinces and territories can configure their building blocks to address variances and ensure alignment with the IPS specification. British Columbia has committed to aligning as close as possible with the Patient Summary sharing work with the PS-CA. The BC Patient Summary Project has focused on an initial Release that meets the minimum requirements as outlined by clinicians. BC Providers in community/clinic settings have not historically shared information digitally outside of their settings. As a result, the BC requirements are expected to evolve as clinicians become more comfortable with sharing of information and of the clinician requirements of a Patient Summary. To read more about the PS-CA:BC, go here. |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform) | ||
PS-ON | 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. |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform) | ||
PS-CA:NB | The PS-CA:NB implementation has adopted the PS-CA FHIR profiles without creating a separate implementation guide. The initial NB Patient Summary release focuses on requirements outlined by NB clinicians, a subset of data from MyHealth Records, and the Patient Mediated Access use case using the CA:SHL profile. To read more about the PS-CA:NB implementation, go here |
| TBD No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform) | ||
PS-AB | The Alberta Patient Summary (PS-AB) is based on the the Pan-Canadian Patient Summary (PS-CA) Standard, and the Canadian Baseline (CA-Baseline). It was developed in collaboration with Canada Health Infoway and with input from Alberta clinicians and solution vendors. The PS-AB attempts to profile in a way that allows the patient summary instances to be conformant to PS-CA, and CA-Baseline without having to formally derive from the profiles in these specifications. To read more about the PS-AB, go here. | Coming soon |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform)Coming soon | |
*To learn more about the Supporting Tools, go here.
...
The Test Cases for Secure Exchange Transactions are designed to validate the interoperability capabilities of the system under test in securely exchanging a Patient Summary. 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 access Gazelle, where you can find the full set of test cases categorized by interoperability profile, actor, and transaction.
...