Versions Compared

Old Version 15

changes.mady.by.user Allana Cameron

Saved on

compared with

New Version Current

changes.mady.by.user Allana Cameron

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Page properties
idPSCAReleases
Release TitlePS-CA v0.2
Release DateJanuary

,

 

Release Type Draft 
Open Review PeriodJanuary 28 - February 14, 2022
Published ContentPS-CA Interoperability Specifications v0.2
Download Specifications (PDF)

PS-CA Specification v0.2

FHIR Implementation Guide v0.2

Companion Guide to Use Cases and Definitions v0.2

Companion Guide to Reference Architecture v0.2

How to Provide Feedback:

...

Excerpt

The Public Review period for the Pan-Canadian Patient Summary Interoperability Specifications v0.2 is now open.

The timeline for Public Review is: January 28 - February 14, 2022.

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 feedback:

  • All Collaborators are invited to document comments using the Public Review Comments PS-CA v0.2 spreadsheet, available here. 
  • Send an email to [email protected], with Subject Line "PS-CA", including the Comments spreadsheet as an attachment.
  • We kindly ask that each organization submit all comments within one spreadsheet submission. 
  • Upon submission, you will receive an acknowledgement email with a reference number. Our team will complete a review of all comments, determine the appropriate disposition for each item and incorporate changes and backlog items into the release notes for v0.3. 

For questions, please contact us at [email protected]

...

Expand
titleWhat guidance does the PS-CA Specification provide for authentication and security?

The PS-CA Specification includes  refers to the IHE IUA profile that manages access tokens used for authorization of access to HTTP RESTful services based on the flows and transactions defined in the OAuth 2.1 Authorization Framework [OAuth 2.1]. It recommends the use of asymmetric (public-key based) methods for client authentication [OAuth 2.1, Section 9.1], but allows other suitable HTTP-based authentication schemes matching the security policy of the Authorization Server [OAuth 2.1, Section 2.3.2].

Expand
titleIs it required that the IUA for authentication between systems be implemented for each of the profiles utilized (e.g., Find Document References ITI-67)?

Implementation of IUA is recommended, but not mandatory. However, when MHD actors are grouped with IUA actors there are additional security and privacy functionality enabled by this grouping and is therefore encouraged.

...