DFT Ballot - This specification is currently in ballot review and subject to change. It is not ready for limited roll-out or production level use. For a full list of available versions, see the Directory of published versions
Use Cases
Overview
This page provides an overview of use cases and workflow scenarios for sharing clinical documents across systems. Jurisdictions may adapt these use cases to fit local implementation needs. As such, the examples provided are illustrative only; they are not prescriptive, nor do they represent all possible implementation approaches. The use cases describe high-level interactions between a Health Care Provider or Patient using a Clinical Solution (e.g., EMR, patient portal) and the Health Information Exchange (HIE). These scenarios outline the business context—or "conversation"—between systems and their users, referred to here as Participants. Participants may be individuals (e.g., health care providers, patients) or systems (e.g., EMRs, HIEs). Detailed interaction flows are defined in Sequence Diagrams.
Each use case includes:
- A scenario description
- Example triggers, preconditions, and postconditions
- A definition of participants (i.e., individuals and systems)
- A use case diagram illustrating interactions between participants
- Use case steps corresponding to the diagram and potential alternate flows.
Use Case Index
The following use cases, prioritized through the pan-Canadian environmental scan, define the current scope of the CA:FeX Specification. Each entry includes a use case ID, name, and summary.
Additional use cases may be introduced in future releases.
| Use Case Name | Description |
|---|---|
| UC-01 Create and Submit Document | A Health Care Provider documents patient information during a care encounter and submits it as a clinical document to the Clinical Data Repository, where it becomes available to other authorized providers. |
| UC-02 Query and Retrieve Document | A Health Care Provider or patient retrieves clinical documents from the Clinical Data Repository, either to support care at the point of service or to obtain a personal copy. |
| UC-03 Create and Submit Data | A Health Care Provider records structured clinical data during a care encounter and submits it to the Clinical Data Repository for use by other authorized providers. |
| UC-04 Query and Retrieve Data | A Health Care Provider or patient retrieves structured clinical data from the Clinical Data Repository for use in care delivery or personal health management. |
| UC-05 Fetch Document References | A clinical system fetches metadata references to available clinical documents, enabling targeted retrieval by Health Care Providers or patients. |
For a view of how different system actors may support services in the context of these use case, including the roles they play and the relevant specifications, see Actor Mapping to Interoperability Specification.