...
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. The purpose of the test cases for PS-CA:BC will ensure that the Patient Summary is formatted and contains the required content according to the PS-CA:BC implementation guide. In support of these test cases, the following documents will be provided:
To read more about the PS-CA:BC, go here. | TBD |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform)TBD | |||||
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). The purpose of the test cases for PS-ON will ensure that the Patient Summary is formatted and contains the required content according to the PS-ON implementation guide. In support of these test cases, the following documents will be provided:
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)Gazelle platform) | ||||||
PS-CA:NB |
| No-Peer (PS-CA Renderer, FHIR Validator, CA:FeX Simulators, and MHD Simulators) Peer-to-Peer (Gazelle platform) | |||||||
PS-AB | Alberta is in the process of developing implementation details to provide to their implementers. Update: The PS-AB will not be tested at the Projectathon 2023. Vendors are being requested to focus on the PS-CA. At such time that the PS-AB is ready, it is expected that minimal configuration of capability in the vendor systems will be needed. To read more about the PS-AB, go here. | Coming soon | Coming soon | PS-CA:NB | TBD | TBD | PS-AB | TBD | TBD |
*To learn more about the Supporting Tools, go here.
...
Test Cases for Secure, Exchange Transactions | |||
|---|---|---|---|
By IHE Profile | Profile Description and Purpose of Test Cases | Actors Involved | Test Case Peer Type & Supporting Tools* |
CA:FeX | 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:FeX is to ensure systems have the ability to create, search and retrieve FHIR documents (e.g., Patient Summary) over the internet in a secure manner. Test cases for CA:FeX will include groupings with other profiles to ensure that patient information is shared securely over the internet (CA:Sec), meets audit requirements (CA:Aud), contains a consistent time (CT) with a median error less than 1 second and is accessed only by authorized users (IUA). To learn more about CA:FeX, you may watch this short video and review the presentation material here: CA:FeX Profile Information Video (mp4), CA:FeX Profile Information Presentation Deck (PDF) To read more technical information about CA:FeX, go here. |
| No-Peer (CA:FeX Client & Server Simulator) Peer-to-Peer (Gazelle platform) |
MHD | The Mobile Access to Health Documents (MHD) Profile defines one standardized interface to health document sharing. This profile is applicable to systems where needs are simple, such as pulling the latest summary for display. The purpose of testing MHD is to ensure systems have the ability to publish and access (i.e. query/retrieve) FHIR documents (e.g., Patient Summary) over the internet in a secure manner. Test cases for MHD will include groupings with other profiles to ensure that patient information is shared securely over the internet (CA:Sec), meets audit requirements (CA:Aud), contains a consistent time (CT) with a median error less than 1 second and is accessed only by authorized users (IUA). To learn more about MHD, you may watch this short video and review the presentation material here: MHD Profile Information Video (mp4), MHD Profile Information Presentation Deck (PDF) To read more technical information about MHD, go here. |
| No-Peer (MHD Client & Server Simulator) Peer-to-Peer (Gazelle platform) |
IUA | The Internet User Authorization (IUA) is an interoperability profile that provides an authorization profile for the HTTP RESTful transactions. Being authorized means that the user, patient, or provider has legitimate access to this HTTP RESTful service. The authorization includes identifying the user and the application that is making the request to the HTTP RESTful server, so that the server can make further access control decisions. The purpose of testing IUA in these test cases is to ensure that the person (e.g., patient, provider, etc. ) and application requesting access to the FHIR document (e.g., Patient Summary) are authorized to have access. To learn more about IUA, you may watch this short video and review the presentation material here: IUA Profile Information Video (mp4), IUA Profile Information Presentation Deck (PDF) To learn more about IUA, go here. |
| No-Peer (IUA Simulator) |
CA:Sec | The CA:Sec (Canadian Network Security) Implementation Guidance specifies the foundational elements needed to securely execute transactions between two systems. It is based on the ATNA profile and aims to bring improvements via loose coupling, and high cohesion, with focus on secure communication. The purpose of testing CA:Sec in these test cases is to ensure that the systems exchanging FHIR documents are able to meet the requirements of secure exchange between systems. To learn more about CA:Sec, you may watch this short video and review the presentation material here: CA:Sec Profile Information Video (mp4), CA:Sec Profile Information Presentation Deck (PDF) To read more technical information about CA:Sec, go here. |
| No-Peer (Gazelle Security Suite, TLS Server and Client Simulators) |
CA:Aud | The CA:Aud (Canadian Audit Trail) Implementation Guidance specifies the foundational elements needed to perform event logging for auditing purposes. It is based on the ATNA profile and aims to bring improvements via loose coupling, and high cohesion, with focus on auditing using modern formats and technologies. CA:Aud defines capabilities to record, store and retrieve audit messages in FHIR format using RESTful operations and other (IHE or non-IHE) methods. The purpose of testing CA:Aud in these test cases is to ensure that the systems exchanging FHIR documents (e.g., Patient Summary) are able to meet the requirements of recording, storing and retrieving audit messages. To learn more about CA:Aud, you may watch this short video and review the presentation material here: CA:Aud Profile Information Video (mp4), CA:Aud Profile Information Presentation Deck (PDF) To read more technical information about CA:Aud, go here. |
| No-Peer (Tested as part of CA:FeX and MHD) |
CT | The Consistent Time Integration Profile (CT) provides a means to ensure that the system clocks and time stamps of the many computers in a network are well synchronized. The purpose of testing CT in these use cases is to ensure the systems exchanging FHIR documents (e.g., Patient Summary) are synchronized with a median error less than 1 second. This provides systems with the ability to properly manage the information and provides clarity for users on the timeline of when the information was recorded. To learn more about CT, you may watch this short video and review the presentation material here: CT Profile Information Video (mp4), CT Profile Information Presentation Deck (PDF) To read more technical information about CT, go here. |
| No-Peer (Scripts provided within the test cases) |
CA:SHL | |||
*To learn more about the Supporting Tools, go here.
...