User Stories / Use Cases

Below is a summary of the descriptions for each use case.

Use Case Description
UC-01: Care Provider views and selects SMART Apps that are of interest A Care Provider wants to view available digital health services (e.g., clinical decision support tools or jurisdictional assets) integrated through SMART Apps within the Point of Care Solution and select the ones that may enhance their clinical workflow.
UC-02: Care Provider Accesses Additional Patient Data via SMART App A Care Provider wants to easily view data not available within their Point of Care Solution for a given patient (e.g., data from the jurisdictional Electronic Health Record (EHR), including lab tests, summaries, and medications).
UC-03: Care Provider Shares Patient Data with a SMART App A Care Provider wants to launch SMART apps from within their Point of Care Solution to access and share relevant patient information with digital health services, such as creating eReferrals, eConsults, or electronic orders, depending on jurisdictional assets.
UC-04: Care Provider Receives External Information via SMART App A Care Provider would like to receive information from external applications, including SMART Apps and jurisdictional assets, back within their Point of Care Solution.

UC-01: Care Provider views and selects SMART Apps that are of interest

Description

A care provider wants to view available applications (e.g., clinical decision support tools, jurisdictional assets, digital health services) integrated through SMART Apps within the Point of Care Solution and select the ones that may enhance their clinical workflow.

Scenario

Dr. Jones, a family physician, recently discovered that third-party SMART Apps have been integrated into the Point of Care Solution they regularly use at their clinic. Curious about the new capabilities, Dr. Jones logs into the Point of Care Solution to explore the available SMART Apps. After reviewing the list, Dr Jones identifies a few apps that may enhance their workflow.

Participants

People Systems
Care Provider: A clinician responsible for delivering care who interacts with SMART Apps to manage clinical tasks like consultations or data review. Point of Care Solution (PoC): The clinical application used by the care provider to access and manage SMART Apps.
App Catalog: A restful API that provides necessary information about approved SMART Apps available within a jurisdiction for integration with the PoC Solution.

Triggers

  • The care provider wishes to see available SMART Apps to determine if there are any opportunities to improve their clinical workflow.

Pre-conditions

  • Care Provider Authenticated: The Care Provider has valid credentials and is authenticated with the PoC Solution.
  • PoC Solution Configured: The Point of Care Solution is able to access and display information.
  • App Catalog Configured: The Point of Care solution is able to retrieve and display the list of SMART Apps contained within the app catalog.

Post-conditions

  • Preferred Apps Updated: The Care Provider is presented with the list of SMART Apps that are available for launch from within their system

Primary Flow

  1. Care Provider using their PoC Solution requests to explore the available SMART Apps that can improve the clinical workflow.
  2. App Catalog provides the available SMART Apps, including the requirements needed to integrate the SMART App within the PoC.
  3. Care Provider using their PoC Solution accesses the available SMART Apps and the SMART App information.
  4. Care Provider identifies the SMART Apps that may be used in their workflow.

Diagram

UC-02: Care Provider Accesses Additional Patient Data via SMART App

Description

A care provider wants to easily view data not available within their Point of Care Solution for a given patient (e.g., data from the jurisdictional Electronic Health Record (EHR), including lab tests, patient summaries, immunization records, and medication history, depending on available assets within the jurisdiction) directly from within their PoC Solution.

Scenario

Dr. Smith, a family physician, is reviewing a patient's recent visit notes in her PoC Solution. She needs to check the latest lab results and immunization records, which are not available within her PoC Solution. Instead of logging into a separate system, Dr. Smith launches the Clinical Data Viewer SMART App directly from her PoC Solution. The SMART App provides seamless access to the patient's data from the jurisdictional EHR. Dr. Smith reviews the lab results, immunization records, and updates her patient notes accordingly.

Participants

People Systems
Care Provider: The family physician who needs to access additional patient data. Point of Care Solution: The clinical application used by the care provider to access and manage patient information.
SMART App: The Clinical Data Viewer app that provides access to additional patient data.
App Launcher: The interface within the PoC Solution that allows the care provider to select and launch SMART Apps.
Jurisdictional EHR System: The system that stores additional patient data.

Triggers

The care provider initiates this use case when they need to access additional patient data not available in their PoC Solution by launching the appropriate SMART App from the App Launcher within the PoC Solution.

Pre-conditions

  • PoC Solution Configured: The PoC Solution is able to load SMART Apps and access the requirements needed to launch the SMART App.
  • Care Provider Authenticated with the PoC: The care provider has valid credentials and is authenticated with the Jurisdictional Identity Provider (IDP).
  • Care Provider Registered with the Jurisdictional EHR: The Care Provider is registered within the Jurisdictional EHR with valid credentials.
  • SMART App Available: The SMART App (e.g., Clinical Data Viewer) is integrated with the PoC and available for use.
  • SMART App Registered with the Jurisdictional EHR: The SMART App is registered with the Jurisdictional EHR and allowed to obtain access to jurisdictional clinical data.

Post-conditions

  • Additional Data Accessed: The care provider successfully views additional patient data from the jurisdictional EHR.

Primary Flow

  1. Care Provider selects a SMART App integrated within the PoC Solution and initiates the SMART App launch.
  2. PoC launches the SMART App passing the current clinical context (e.g., the current patient, encounter, etc.).
  3. Care Provider is prompted to log in using their jurisdictional credentials, if not already authenticated with the Jurisdictional EHR.
  4. SMART App authenticates against the PoC and obtains authorization to access PoC data.
  5. SMART App authenticates against the Jurisdictional EHR and obtains authorization to access jurisdictional data.
  6. SMART App retrieves the jurisdictional clinical data and displays additional data to the user.
  7. Care Provider has access to the additional clinical data from the jurisdictional EHR system.

Diagram


UC-03: Care Provider Shares Patient Data with a SMART App

Description

A care provider wants to launch SMART apps from within their Point of Care Solution to access and integrate digital health services, such as creating eReferrals, eConsults, electronic orders, or electronic forms. The specific services depend on what is available in their jurisdiction. In this use case, the care provider needs to share essential patient information for a particular clinical task using existing data standards, like the Pan-Canadian Patient Summary or the eReferral/eConsult standard, where applicable.

Scenario

Dr. Lee, a family physician, is seeing a patient who has noticed a suspicious mole on their skin that has changed in size and color. Concerned about the potential for melanoma, Dr. Lee decides to seek the opinion of a dermatologist using the eConsult SMART App. Dr. Lee launches the eConsult SMART App from the App Launcher within the PoC Solution. The PoC Solution generates an eConsult-specific set of data for the patient in context, to be supplied to the SMART App. Dr. Lee reviews the eConsult request form with all of the necessary data pre-populated within the eConsult SMART App. After completing the consultation, Dr. Lee validates and submits the eConsult.

This scenario demonstrates a typical use case where a care provider launches an app (e.g., eConsult) from their Point of Care Solution, shares critical patient information, and completes a clinical task. It highlights the flexibility of the framework, supporting various digital health services, all following similar flows.

Participants

People Systems
Care Provider: The family physician initiating the eConsult and sharing patient details with the specialist. Point of Care Solution: The clinical application used by the care provider to access and manage SMART Apps.
App Catalog: A restful API that provides necessary information about approved SMART Apps available within a jurisdiction for integration with the PoC Solution.
SMART App: The eConsult app facilitating secure communication.
Jurisdictional IDP: Authenticates the care provider’s identity.
App Launcher: The interface within the PoC Solution for selecting SMART Apps.

Triggers

The care provider initiates this use case when they need to share patient information or complete a clinical task using a digital health service by launching the appropriate SMART App from the App Launcher within the PoC Solution.

Pre-conditions

  • PoC Solution Configured: The PoC Solution is able to load SMART Apps and access the requirements needed to launch the SMART App.
  • Care Provider Authenticated with the PoC: The care provider has valid credentials and is authenticated with the PoC Solution.
  • Care Provider Registered with the Jurisdictional EHR: The Care Provider is registered within the Jurisdictional EHR with valid credentials.
  • SMART App Available: The SMART App (e.g., eConsult) is integrated with the PoC and available for use.
  • SMART App Registered with the Jurisdictional EHR: The SMART App is registered with the Jurisdictional EHR and allowed to obtain access to jurisdictional clinical data.

Post-conditions

  • Task Successfully Submitted: The care provider successfully validates, signs, and submits the task (e.g. eConsult request for a dermatological assessment).

Primary Flow

  1. Care Provider selects a SMART App integrated within the PoC Solution and initiates the SMART App launch.
  2. PoC Solution presents the Care Provider with the necessary clinical data for the patient to be shared with the SMART App.
  3. PoC launches the SMART App passing the current clinical context (e.g., the current patient, encounter, relevant clinical data for workflow, etc.).
  4. Care Provider is prompted to log in using their jurisdictional credentials, if not already authenticated with the Jurisdictional EHR.
  5. SMART App authenticates against the PoC and obtains authorization to access PoC data.
  6. Care Provider completes the clinical task in the SMART App using the data that was supplied by the PoC Solution.

Diagram

UC-04: Care Provider Receives External Information via SMART App

Description

A care provider would like to see updated clinical patient information in the PoC solution after clinical data is updated in the SMART App that is integrated with the PoC. The Care Provider has the ability to view the updated clinical data (e.g., view or save selected information into the Patient Chart) in the PoC.

Scenario A: Basic SMART on FHIR Flow

Dr. Patel, a family physician works within their Point of Care Solution which received new lab results for a patient that have been delivered via a SMART App. After reviewing the results, Dr. Patel decides to save the key findings into the patient’s chart.

Participants

People Systems
Care Provider: The physician who is interacting with the PoC and receives access to new patient information. Point of Care Solution (PoC): The clinical application used by the care provider to access and manage patient information.
SMART App: An app integrated with the PoC through SMART on FHIR that provides externally sourced clinical data (e.g., clinical viewer).

Triggers

The SMART App has new or updated clinical data that needs to be stored in the PoC system.

Pre-conditions

  • PoC Solution Configured: The Point of Care Solution is able to load and access SMART Apps.
  • Care Provider Authenticated: The Care Provider has valid credentials and is authenticated with the PoC Solution.
  • SMART App Authorized: The SMART App is registered with the PoC and has the appropriate permissions to write data to the PoC FHIR server.

Post-conditions

  • External Information Received: The care provider successfully reviews and integrates external information into the patient’s record.

Primary Flow

  1. SMART App updates clinical data in PoC FHIR server based on new information received .
  2. PoC provides confirmation to the SMART App that the clinical data was successfully updated.
  3. SMART App receives confirmation and concludes the transaction.
  4. Care Provider has the ability to review the externally sourced clinical data and save key information into the patient’s chart.

Diagram

Scenario B: SoFA Flow using Notifications

Dr. Patel, a family physician works within their Point of Care Solution which received an event notification indicating that new lab results for a patient have been written by a SMART App within the SMART on FHIR accelerator FHIR server. Based on the notification, the PoC saves the lab result information within the PoC system.

Participants

People Systems
Care Provider: The physician who is interacting with the PoC and receives access to new patient information. Point of Care Solution (PoC): The clinical application used by the care provider to access and manage patient information.
SoFA: HALO SMART on FHIR Accelerator.
SMART App: An app integrated with the PoC through SMART on FHIR that provides externally sourced clinical data (e.g., clinical viewer).

Triggers

The SMART App has new or updated clinical data that needs to be stored in the PoC system.

Pre-conditions

  • PoC Solution Configured: The Point of Care Solution is able to load and access SMART Apps and is configured to use the HALO SoFA flow.
  • PoC Solution Subscribed to Notifications: PoC Solution is subscribed to the SoFA Topic, to receive notifications when new data is received in the SoFA.
  • Care Provider Authenticated: The Care Provider has valid credentials and is authenticated with the PoC Solution.
  • SMART App Authorized: The SMART App is registered with the SoFA and has the appropriate permissions to write data to the SoFA FHIR server.

Post-conditions

  • External Information Received: The PoC successfully receives and integrates external information into the patient’s record.

Primary Flow

  1. SMART App updates clinical data in SoFA FHIR server based on new information received.
  2. SoFA sends notification to the PoC Solution and provides full access to the updated clinical data.
  3. PoC Solution receives the notification and processes the updated clinical data.
  4. PoC Solution saves the clinical data updates into the local database.
  5. PoC sends confirmation to the SoFA that the clinical data was successfully processed and updated.
  6. SoFA receives confirmation, reconciles the clinical records, and updates the data in the SoFA FHIR server.
  7. SoFA provides confirmation to the SMART App that the requested write operation was received.
  8. SMART App receives confirmation and concludes the transaction.
  9. The Care Provider has the ability to review the externally sourced clinical data and save key information into the patient’s chart.

Diagram