How to Provide Feedback

This release, PS-CA v2.0.0 DFT-Ballot, has been published for stakeholders to begin working with, in preparation for the next Projectathon/Connectathon in Feb 2025. This will allow stakeholders to gain experience with this release between October-December and provide their feedback as part of a formal ballot cycle, which is scheduled to run from December 2, 2024, to January 17, 2025.

In the meantime, If you have feedback on the PS-CA v2.0.0 DFT-Ballot, to be considered for a future release, you can now submit your feedback via Jira as defined below;

• To submit feedback, you must register as a user on Infoway’s InfoCentral, be an active member of a working group, and be granted access to the JIRA projects.
• To register on the InfoCentral website, go to: https://infocentral.infoway-inforoute.ca. Click on the Register link and follow the instructions to create an account.
• Once registered in InfoCentral, and the Patient Summary Working Group, you can request access to Jira directly in a working group meeting, or by emailing [email protected].
• To access Jira, go to: https://informs.infoway-inforoute.ca (Note: this link will only work if you have been granted access to JIRA).
• Submit your feedback on Jira. You will receive automatic notifications when your submissions receive comments or reach milestones during the review process.
• All collaborators are encouraged to browse through previously submitted feedback to see if a topic has already been discussed.

Please find more information on specification feedback by clicking on this link: pan-Canadian Interoperability Specifications Feedback

If you have any questions, issues, or comments related to specification feedback, please reach out to [email protected]

Release Notes

FHIR Implementation Guide Change Log

Changes to the FHIR Implementation Guide are documented in the Canadian FHIR Registry, PS-CA project, located here.

PS-CA Specifications

• No changes

Companion Guide: Use Cases and Definitions

• Updated UC-02 diagram; removed specific consent steps, with consent now assumed to be captured under step 3. An example has been added to clarify this step.

Companion Guide: Reference Architecture

• No changes