...
An exciting new feature at this Projectathon will be the ability to validate the national (PS-CA) and harmonized provincial Patient Summary specifications from two leading jurisdictions: Alberta (PS-AB) and Ontario (PS-ON).
- In addition to testing the PS-CA, test cases will validate the PS-AB and PS-ON specifications, which are very closely aligned to the PS-CA and should be supported by minimal configuration of capability in the vendor systems. The configuration details are provided in the Data Configuration Guide available Guide available on the Tools and Training page.
- The test cases will highlight where configuration is needed and test that the configuration is applied properly, based on claimed vendor conformance.
- The Projectathon will offer an assessment of the Patient Summary document against the ON and AB implementation guidance as represented in the PS-ON and PS-AB specifications, in addition to the PS-CA.
...
- Clinical Data Set for PS-CA: a clinical data set that represents minimum data requirements for PS-CA.Clinical Data Set for PS-AB: a clinical data set that represents minimum data requirements for PS-AB.
- Clinical Data Set for PS-ON: a clinical data set that represents minimum data requirements for PS-ON.Comprehensive
2. PS-CA
...
Secure, Exchange Transactions
This area of testing will focus on validating the recommended secure exchange methods of the FHIR summary document as presented in the Reference Architecture (RA v0.1.1 DFT), 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.
There are two categories of integration profiles (see table Test Cases for Secure, Exchange Transactions for more information):
- Core integration profiles: CA:FeX and MHD
- Supporting integration profiles: CA:Sec, CA:Aud (Canadian implementation guidance for ATNA), CT, and IUA
Implementation patterns of these integration profiles may differ from jurisdiction to jurisdiction and information exchange channels may vary in terms of their security footprint. Therefore, the Projectathon test cases have been organized into two categories:
- Category 1: Test cases that test individual actor capabilities in isolation. E.g., how a system can handle encrypted transactions, how a system can handle a CA:FeX transaction, how a system can handle an OAuth 2 token exchange, etc.
- Category 2: Complex test cases that group individual actor capabilities with other relevant actor capabilities to simulate real world scenarios
2. PS-CA Secure, Exchange Transactions
This area of testing will focus on validating the recommended secure exchange methods of the FHIR summary document as presented in the Reference Architecture (RA v0.1.1 DFT), 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.
There are two categories of integration profiles (see table Test Cases for Secure, Exchange Transactions for more information):
- Core integration profiles: CA:FeX and MHD
- Supporting integration profiles: CA:Sec, CA:Aud (Canadian implementation guidance for ATNA), CT, and IUA
Implementation patterns of these integration profiles may differ from jurisdiction to jurisdiction and information exchange channels may vary in terms of their security footprint. Therefore, the Projectathon test cases have been organized into two categories:
- Category 1: Test cases that test individual actor capabilities in isolation. E.g., how a patient summary creator system can handle encrypted transactions, how a system can handle a CA:FeX transaction, how a system can handle submit the document to a repository by using an OAuth 2 token exchangeintegration, etc.
- Category 2: Complex test cases that group individual actor capabilities with other relevant actor capabilities to simulate real world scenarios. E.g., how a patient summary creator system can submit the document to a repository by using an OAuth 2 integration, etc.
Testing the Testing the Secure, Exchange Transactions
...
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* | Test Case Peer Type & Supporting Tools* | |||||
PS-CA | The Projectathon 2023 will focus on interoperability demonstrations based on the pan-Canadian Patient Summary (PS-CA v1.0.0 TI) and the associated pan-Canadian FHIR Exchange (CA:FeX v1.0.0 TI) specifications, both ready for trial implementation. 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-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 configurations will be needed. | The Projectathon 2023 will focus on interoperability demonstrations based on the pan-Canadian Patient Summary (PS-CA v1.0.0 TI) and the associated pan-Canadian FHIR Exchange (CA:FeX v1.0.0 TI) specifications, both ready for trial implementation. 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-AB | Alberta is in the process of developing implementation details to provide to their implementers. At the time of the September 2022 release, details like usage notes, comments, mappings, and additional constraints have been applied within PS-AB profiles that are derived from the PS-CA profiles. The purpose of the test cases for PS-AB will ensure that the Patient Summary is formatted and contains the required content according to the PS-AB implementation guide. In support of these test cases, the following documents will be provided: To read more about the PS-AB, go here. |
|
| N/A 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). 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) | ||||||
...