The purpose is to describe the use cases and workflow scenarios for sharing a patient summary profile across solutions. Each jurisdiction may have implementation variances within the use cases. Therefore, these use cases provide examples and are not meant to be inclusive of all possible implementation choices and do not represent required implementation choices. The use cases provide high-level interactions between the Health Care Providers, their Health Records System and other Health Records Systems. Use cases provide the business description or "conversation" between the system(s) and its user(s), known as Participants. Participants can be people (e.g., health care providers, patients, etc.) or systems (e.g., EMR, EHR Repository, etc.). Please note that detailed interactions are defined in the pan-Canadian Patient Summary - Companion Guide to Reference Architecture.
Each use case will include:
- use case scenario,
- examples of use case triggers, pre and post conditions,
- who the participants are (i.e., people and systems),
- a use case diagram to provide a visual representation of the interactions between participants,
- use case steps corresponding to the diagram and potential alternate flows; and
- reference to the corresponding business requirements.
Use Case Index
This section includes a proposed list of use cases which were identified as being priority use cases in the pan-Canadian environmental scan. Subsequently, through collaboration with the participating Canadian jurisdictions, the use case scope was further refined into priorities for the initial releases and those which will be included in future releases.
The scope for this release of the pan-Canadian Patient Summary – Interoperability Specifications has been defined to include use cases UC-01, UC-02 and UC-03.
The list below includes the use cases' ID, name and description. Following each use case is a list of the Canadian jurisdictions that have identified the use case as being applicable to their Patient Summary implementation for Release 1 or beyond.
| Use Case ID | Use Case Name | Use Case Description | Identified by: |
|---|---|---|---|
| UC-01 | HCP Creates a PS-CA | A Health Care Provider in any care setting creates a Patient Summary for use at point of care, which is made available to Patient Summary consumers. | AB, BC, NL, ON, SK |
| UC-02 | HCP Views/Consumes a PS-CA | A Health Care Provider in any care setting , views and uses a PS-CA at the point of care. | AB, BC, NL, ON, SK |
| UC-03 | Patient Views/Consumes a PS-CA | A Patient or Subject of Care accesses/views and can obtain a copy of their own PS-CA. | AB, BC, NL, ON |
FUTURE SCOPE
In addition to the use cases identified as in scope for this release of the pan-Canadian Patient Summary – Interoperability Specifications, a set of use cases were identified for future consideration. Uses cases UC-04, UC-05 and UC-06 will be candidates for subsequent releases within the PS-CA Specifications roadmap.
| Use Case ID | Use Case Name | Use Case Description | Identified by: |
|---|---|---|---|
| UC-04 | HCP Sends PS-CA to another HCP as part of a Clinical Workflow (e.g. eReferral). | A Health Care Provider creates/produces a PS-CA and sends the PS-CA with other clinical documentation as part of a clinical care workflow (e.g. referral, consult etc.). | AB, BC, NL, ON, SK |
| UC-05 | Patient Presents PS-CA to HCP | A Patient or Subject of Care presents their PS-CA to a HCP, who may view/consume the PS-CA, to support care. | AB, BC, NL, ON, SK |
| UC-06 | HCP requests PS on Demand | A Health Care Provider in any care setting requests access to a real-time, on-demand PS-CA to be used at the point of care or as part of a clinical workflow (e.g. referral). | ON |