Business Context Index > Use Case

Use Cases

The use cases below provide a basic illustration of how actors interact with the DHDR using the Consumer Query.
When an access request is made to the DHDR solution for a patient’s drug and pharmacy service history, the DHDR solution uniquely identifies the patient based on the supplied patient identifiers and returns that patient’s drug and pharmacy service events history to the calling system. The calling system can then use the results to create a drug and pharmacy service profile for the patient.

Actors

Table- Use Case Participants

Participant Type Description
Consumer Human A person (patient, designate, delegate user) who interacts with the system via a consumer application to search a person’s drug and pharmacy service information in DHDR.

Patient: A user accessing their personal drug and pharmacy service information in DHDR

Designate: A user authorized to access the DHDR as the patient’s substitute decision-maker

Delegate: A user granted access and authority by a patient or designate to access the patient’s DHDR information
Consumer Application system A digital application used by the consumer to search drug and pharmacy service information in DHDR. The application maintains, manages and validates the user information and credentials prior to the request being sent to DHDR.
Consumer Gateway system An interface layer that processes security and user based information received from a consumer application. The Consumer Gateway authorizes the query to be processed by DHDR.
DHDR system A provincial information source of medication and pharmacy service information (EHR asset). Currently the DHDR includes publicly funded drug and pharmacy services and all monitored drugs (regardless of payor) contributed by the Ministry of Health. DHDR exposes service endpoints to allow access to DHDR information.
COVaxON system The Ministry of Health’s provincial solution for COVID-19 vaccination information. A subset of COVID-19 vaccination information is made available through the DHDR.

UC1 – Consumer requests DHDR information - Information successfully returned

Consumer requests DHDR information via consumer application with a specific date range and a health card number. The record for the patient (HCN) is found in DHDR and/or COVaxON. Information is successfully returned by DHDR via Consumer Gateway.

Steps:

  1. Consumer enters search criteria (Ontario Health Card (HCN) Number and dispensed date/search period) in Consumer Application.
  2. Consumer Application formulates the search request and submits it to Consumer Gateway.
  3. Consumer Gateway authorizes and validates the request and forwards to DHDR.
  4. DHDR searches in DHDR database (using HCN and search time period) and calls COVaxON for COVID-19 vaccination records.
  5. Information is found in DHDR and/or COVaxON.
  6. DHDR returns information from the DHDR and/or COVaxON for the specified search parameters to the consumer application via Consumer Gateway.
  7. Consumer Application displays the relevant information received from Consumer Gateway to the consumer.

    Alternate Workflow (not expanded):
  1. DHDR Consumer requests DHDR information without specifying dispensed date parameter
    1. DHDR returns information from the DHDR and/or COVaxON for the default parameter of 120 days to the consumer application via Consumer Gateway.
  2. No records found
    1. DHDR returns message indicating no records found for search parameters.

UC2 –Consumer requests details of a specific DHDR record

After successful return of DHDR records, consumer requests details of a specific DHDR record returned via Consumer Application (e.g., selects one record from list of records).

Assumption: Consumer application does not save/store bundled search response from the DHDR

Steps:

  1. Consumer performs an action in Consumer Application to view details of a specific DHDR or COVaxON record.
  2. Consumer Application formulates the request (using the Medication Dispense ID) and submits it to Consumer Gateway.
  3. Consumer Gateway authorizes and validates the request and forwards to DHDR.
  4. DHDR searches in DHDR database or calls COVaxON.
  5. Information is found in DHDR or COVaxON.
  6. DHDR returns information from the DHDR or COVaxON to the consumer application via Consumer Gateway.
  7. Consumer Application displays the relevant information received from Consumer Gateway to the consumer.

UC3 –Consumer requests DHDR information - COVaxON information is not returned (COVaxON is not available)

Consumer requests DHDR information and COVaxON information is not successfully returned because COVaxON is not available. DHDR information is returned.

Steps:

  1. Consumer enters search for DHDR information.
  2. Consumer Application formulates the request and submits it to Consumer Gateway.
  3. Consumer Gateway authorizes and validates the request and forwards to DHDR.
  4. DHDR searches in DHDR database (using HCN and search time period) and calls COVaxON for COVID-19 vaccination records
  5. Call to COVaxON API is unsuccessful (e.g., DHDR query times out or COVaxON API not available).
  6. DHDR returns relevant DHDR results (if found) and notification message that COVID-19 vaccination information is unavailable to Consumer Application via Consumer Gateway.
  7. Consumer Application displays the relevant information received, including notification message, from Consumer Gateway to the consumer.

UC4 –Consumer requests DHDR information - Information is not successfully returned

Consumer requests DHDR information via Consumer application and information is not successfully returned by DHDR via Consumer Gateway due to validation or system failures

Workflows not expanded:

  1. Consumer Application request fails validation in Consumer Gateway (e.g., Consumer Application user is not authorized to access application)
    1. Negative response returned to Consumer
  2. Consumer Application request fails validation in DHDR (e.g., Consumer Application request contains date range where TO date value is prior to FROM date value)
  3. DHDR or Consumer Gateway not available
    1. Error messages returned to Consumer