PS-CA Use Case Overview 


The scope for this release of the pan-Canadian Patient Summary – Interoperability Specifications have been defined to include use cases UC-01, UC-02,UC-03, UC-04, and UC-05.

The list below includes the use case's ID, name, description, and purpose. Participating Canadian jurisdictions have identified these use cases as applicable to their Patient Summary implementation for Release 1 or beyond. 

Use Case IDUse Case NameUse Case DescriptionPurpose
UC-01HCP Creates a PS-CA

A Health Care Provider (HCP) in any care setting creates a Patient Summary for use at point of care, which is made available to Patient Summary consumers.

To ensure that the most current patient information is available to other HCPs who may provide care in the future, supporting continuity of care and informed clinical decision-making. 

Provides the ability for a HCP to share the most current information about their patient in their health records system (e.g., EMR) to a central location, where other authorized HCPs can access the patient summary. 

UC-02HCP Views/Consumes a PS-CAA HCP in any care setting , views and uses a PS-CA at the point of care.Provides the ability for authorized HCPs to request (i.e., query), retrieve and view an existing patient summary (e.g., PDF document) that has been stored in a central location (e.g., EHR). 

UC-03


Patient Views/Consumes a PS-CAA Patient or Subject of Care accesses/views and can obtain a copy of their own PS-CA.

Provides the ability for patients to access and view their patient summary. 

UC-04HCP requests PS-CA on-demand 

A HCP in any care setting requests a patient summary to be created at the time of the request (i.e., on-demand), consisting of the patient's most recent health information from an available data source(s) to be used at the point of care or as part of a clinical workflow.


Provides the ability for a HCP to generate a patient summary at the time it is requested. This means retrieving a patient’s most current health data from available sources (i.e., CDR, EHR) when needed, ensuring timely access to information for clinical decision-making and patient care.  

UC-05Patient Mediated Access and Exchange of their Patient Summary. 

A patient, via a patient-facing application, requests access to a shareable copy of their patient summary. Subsequently, the patient provides access to their encrypted patient summary via the QR code on their mobile device or by sharing a secure Verifiable Health Link (VHL), (e.g., via email) at the point of care (e.g., walk-in clinic, emergency department).  The HCP scans the QR code or accesses the VHL shared by the patient, addressing any security prompts, such as entering a passcode if required, and then may proceed to view/utilize and consume the patient summary.

Provides the ability for a patient to request access to their Patient Summary for sharing with a health care provider using a QR code


The Use Case Actors and the Services that are used by this specification for sharing Patient Summaries are described at a functional level in the Patient Summary – Companion Guide to Use Cases and Definitions. Stakeholders who wish to understand the mapping of Use Case Actors to business requirements and recommended IHE Profiles are recommended to read the pan-Canadian Patient Summary – Companion Guide to Use Cases and Definitions and the  pan-Canadian Patient Summary – Companion Guide to Reference Architecture.

Design Constraints & Assumptions


The following design constraints and assumptions exist for this release:

  • All Use Case Actors/Users are logged in to the system. The Use Case Actors/Users are authenticated and appropriately authorized for all data exchange transactions.
  • The implementation patterns in-scope will be based on the MHD IHE Profile or CA:FeX Interoperability Specifications that are being developed for FHIR Health Information Exchange (HIE) Pattern. Additional details about these profiles can be found in the pan-Canadian Patient Summary – Companion Guide to Reference Architecture.

Additional information on design constraints and assumptions can be found in the pan-Canadian Patient Summary – Companion Guide to Use Cases and Definitions.

  • No labels