A system conforming to this Core Interoperability Specification shall claim conformance at the level of a Use Case Actor (first columns of Tables 1.1, 1.2, 2.1, 2.2, 3.1 and 3.2). A system may claim conformance to one or more Use Case Actors among:

  • PS-CA Producer
  • PS-CA Consumer
  • Document Repository (Local or Central)
  • Central Infrastructure
  • Patient Portal

PS-CA Producer and PS-CA Consumer use case actor roles will primarily be taken up by EMR clinical solution vendors. Document Repository and Central Infrastructure use case actor roles can be taken up either by EMR clinical solution vendors or jurisdictions depending on the implementation approach that the jurisdiction decides to adopt. Similarly, the Patient Portal use case actor can be taken up either by a vendor or jurisdiction depending on the approach and policies defined regarding patient/subject-of-care access to their patient summary.

In order to implement a system that fully supports the pan-Canadian Patient Summary Interoperability Specifications v1 Trial Implementation, the system shall be able to claim conformance to 'Required' services and it's associated requirements as defined in Core Interoperability Specification Requirements.

OpenAPI Specification 

It is recommended to use the OpenAPI UI to access the interactive API documentation. The API allows developers to test API calls directly in the browser. There are two APIs:

  • OpenAPI for MHD: available here
  • Open API for CA:FeX: available here

Constraints on PS-CA Use Case Actors Using Two Implementation Patterns 

The pages that follow will describe the constraints on PS-CA Use Case Actors for two implementation patterns below: 

  1. Option 1 - Document Repository/Registry Pattern Using MHD Profile
  2. Option 2 - FHIR Health Information Exchange (HIE) Pattern Using CA:FeX


  • No labels