The purpose is to describe the use cases and workflow scenarios for sharing clinical documents across solutions. Each jurisdiction may have implementation variances within the use cases. Therefore, these use cases do not represent required implementation choices, nor are they representative of all possible implementation choices. These uses cases are to be considered as examples. The use cases provide high-level interactions between a Health Care Provider or Patient using a Clinical Solution (e.g., EMR, Patient Portal, etc.) and the HIE. 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.) using a Clinical Solution (e.g., EMR, Patient Portal) or systems (e.g., HIE, etc.). Please note that detailed interactions are defined in the Reference Architecture section of this document.

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
  • 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. Additional use cases will be defined in future releases.

The scope for this release of the CA:FeX Specifications has been defined to include use cases UC-01 and UC-02.

The list below includes the use cases a Use Case ID, name and description of the use case.  

Use Case IDUse Case NameUse Case Description
UC-01Create and Submit DocumentA Health Care Provider, in any care setting, adds Patient clinical information for use at point of care, which is made available to other authorized HCPs.
UC-02Query and Retrieve DocumentQuery and retrieval of clinical documentation performed by a Health Care Provider for use at the point of care or by the Patient themselves to obtain a copy of their own personal health information.

Requirement Priority Definitions

PriorityDefinition
SHALL
  • used to indicate a required requirement.
SHOULD
  • used to indicate that a requirement is recommended and should be considered as best practice for implementation, but not required (i.e., it is optional) for implementation. 
  • No labels