Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The ballot release of the Pan-Canadian Patient Summary
Page properties
idPSCAReleases
Release TitlePS-CA v1.1.0 DFT
Release Date

 

Release Type Draft 
Open Review Period
December 15 - February 14, 2024
N/A
Published ContentPS-CA Interoperability Specifications v1.1.0 DFT
Download Specifications (PDF)

How to Provide Feedback: 

-Ballot is now available!

The timeline for ballot submissions is January 15 - February 14, 2024.

You may review the PS-CA Specifications in the following formats:

  • Download the PS-CA specifications in PDF format from the corresponding links in the table above or on the Release page
  • Review the PS-CA Specifications in InfoScribe, from the corresponding link in the table above or on the Release page.

How to submit your ballot submission:

How to Provide Feedback: 


 If you have feedback on

All Collaborators are invited to document their ballot comments using

the PS-CA v1.1.0 DFT

-Ballot Submission spreadsheet, available here
  • Send an email to [email protected], with Subject Line "PS-CA", including the PS-CA v1.1.0 DFT-Ballot Submission spreadsheet as an attachment.
  • We kindly ask that each organization submit all comments within one spreadsheet submission. 
  • Upon submission, you will receive an acknowledgment email with a reference number. Feedback will be triaged by the Infoway Lead to support the Patient Summary Working Group with decisioning/voting blocks.
  • , 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 a 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]

    For questions, please contact us at [email protected]

    To learn more about the balloting cycle process, please visit the IO Specifications Publication Model page.

    Release Notes:


    This release, PS-CA v1.1.0 DFT-Ballot, is a minor release reacting to the jurisdictional needs, ensuring that the pan-Canadian Patient Summary specifications stay in alignment with the jurisdictional implementations.

    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

    • Updated the Preface to reflect the purpose of this minor release.Updated the Preface to represent the addition of the Diagnostic Results Data Domain. More details regarding this change can be found in the FHIR Implementation Guide Change Log abovePS-CA data domains table legend to include the meaning of the  "+" symbol in the table comparing IPS-UV to PS-CA for clarification.
    • Updated the interoperability conformance requirements table format to ensure proper alignment and accommodate headers.
    • Added a note to the security consideration section of PS-CA Actor Conformance, Option 2 for implementers. This note highlights that organizations supporting APIs compliant with the specifications have a responsibility to ensure that the access control policies they implement are technically feasible within the underlying software.

    Companion Guide: Use Cases and Definitions

    • No changes

      Updated the pre-conditions of UC-03 to exclude the reference to UC-06 as it is out of scope for this release.

    Companion Guide: Reference Architecture

    • No changes