Use Case Overview
This section describes the two Use Cases for the FHIR Health Information Exchange (HIE) Implementation Pattern, including all design constraints and assumptions as well as the flows of information that will be specified in this pan-Canadian CA:FeX Interoperability Specifications v1 Trial Implementation document. This section also introduces the scenarios that describe how the specified workflows may be used in the Canadian eHealth context.
In-Scope
The following Use Cases are in scope for Release 1 of the pan-Canadian CA:FeX Interoperability Specifications v1 Trial Implementation:
- UC-01 Create and Submit Document
- UC-02 Query and Retrieve Document
Use Case Actors and Services
The Use Case Actors and the Services that are used by this specification are described below. Additional information can be found in the Core Interoperability Specifications Requirements section.
Use Case Actors and Descriptions
| Actor Name | Description / Definition |
|---|---|
Producer | A health records system (e.g., EMR, HIS, CIS, PHR, or EHR) that creates/produces clinical data in response to a request from an authorized health care provider, the subject of care or another authorized health records system. |
Consumer | A health records system (e.g., EMR, HIS, CIS, PHR, Patient Portal or EHR) that enables access to or receipt of clinical data by an authorized health care provider or the subject of care/patient. |
Clinical Data Repository (Local or Central) | A Clinical Data Repository is a shared storage space for clinical documents that can be hosted locally (e.g., at the data producer) 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. |
Use Case Actor Mapping
| Actor Name | UC-01 | UC-02 |
|---|---|---|
Producer | x | |
Consumer | x | |
Clinical Data Repository (Local or Central) | x | x |
Central Infrastructure | x | x |
Design Constraints & Assumptions
The following design constraints and assumptions exist for the pan-Canadian CA:FeX Interoperability Specifications:
- 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.
- Our recommendation is that the Use Case Actors/Users obtain a valid access token from the Authorization Server that is used within each transaction and is based on the IUA IHE Profile.
- Vendors or jurisdictions may decide not to implement optional IHE profiles such as IUA, ATNA and CT, however it is highly recommended that areas pertaining to authentication, auditing and security are being addressed using solutions that currently exist in their respective enterprise architecture.
- Local data sources are in scope for Release 1.
- There may be exceptions to the data source of some of the clinical data across jurisdictions in Canada. For example, for some jurisdictions, the immunization data will be pulled from the provincial immunization repository.