PS-CA Use Case Overview
This section describes the three pan-Canadian Use Cases, including all design constraints and assumptions as well as the flows of information that will be specified in this specification. This section also introduces the scenarios that describe how the specified workflows may be used in the Canadian eHealth context.
In-Scope
Stakeholder engagement has identified 3 prioritized common use cases for Release 1. These use cases are aligned within the participating jurisdictions and are in-scope of the PS-CA project:
| PS-CA Use Cases In-Scope for Release 1 | AB | BC | NL | ON | SK |
|---|---|---|---|---|---|
1) Health Care Provider (HCP) Creates a Patient Summary-CA | x | x | x | x | x |
| 2) Health Care Provider (HCP) Views and Uses a Patient Summary-CA | x | x | x | x | x |
| 3) Patient Accesses and Views their Patient Summary-CA | x | x | x | x |
Additionally, all the business requirements of the pan-Canadian Patient Summary Interoperability Specifications that are testable in Release 1 are in-scope. More information on this can be found in the Patient Summary – Companion Guide to Use Cases and Definitions.
Out-of-Scope
The following Use Cases are not in-scope for this release and will be addressed in future releases.
PS-CA Use Cases Out-of-Scope:
- Healthcare Provider (HCP) Sends a Patient Summary-CA to another Healthcare Provider (HCP) as part of a Clinical Workflow (e.g., eReferral)
- Patient Presents Patient Summary-CA to Healthcare Provider (HCP) in Another Jurisdiction
- Healthcare Provider (HCP) requests Patient Summary-CA on Demand
In addition, all the business requirements of the pan-Canadian Patient Summary Interoperability Specifications that are not testable in Release 1 are out-of-scope. More information on this can be found in the Patient Summary – Companion Guide to Use Cases and Definitions.
Use Case Actors and Services
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. A summary is provided in the following tables:
Use Case Actors and Descriptions
| Actor Name | Description / Definition |
|---|---|
PS-CA Producer | A health records system (e.g., EMR, HIS, CIS, PHR, or EHR) that creates/produces a Patient Summary-CA in response to a request from an authorized health care provider, the subject of care or another authorized health records system. |
PS-CA Consumer | A health records system (e.g., EMR, HIS, CIS, PHR, or EHR) that enables access to or receipt of a Patient Summary-CA by an authorized health care provider or the subject of care/patient. |
Document Repository (Local or Central) | A document repository is a shared storage space for clinical documents (e.g., Patient Summaries) that can be hosted locally or at the Central Infrastructure and can be accessed by authorized users. |
Central Infrastructure | A Central Infrastructure collects health information from participating organizations and stores the information in a centralized place. The Infrastructure also provides access control. Typically, the Central Infrastructure is under jurisdictional control. |
Patient Portal | A patient portal is a web-based access point that enables secure patient access to personal health information and other self-serve health IT services. *Note: Patient Portal is also comparable to the PS-CA Consumer role; however, for Use Case 3, the Patient Summary is viewed by the subject of care. |
Note: A system may assume more than one of the Actor roles defined in the Use Case Actors and Descriptions table.
Use Case Actor Mapping
| Actor Name | UC-01 | UC-02 | UC-03 |
|---|---|---|---|
PS-CA Producer | x | x | |
PS-CA Consumer | x | ||
Document Repository (Local or Central) | x | x | x |
Central Infrastructure | x | x | x |
Patient Portal | x |
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.
- For specific Canadian implementation guidance on IHE profiles (e.g. IUA), refer to the RA v0.1.1 DFT.
- PS-CA is created from local data sources.
- There may be exceptions to the data source of some of the data domains of the Patient Summary-CA across jurisdictions in Canada. For example, for some jurisdictions, the immunization data will be pulled from the provincial immunization repository.
- 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.