Business Model

Context

The Digital Health Drug Repository (DHDR) is a provincial source of medication and pharmacy service information. Currently, the DHDR includes publicly funded drug and pharmacy services, and all monitored drugs (regardless of payor) contributed by the Ministry of Health.

The DHDR is being expanded to include additional personal health information from two new contributing sources – dispensed medication and pharmacy service information from community pharmacies and administered medication information from hospitals.

The DHDR Consumer Query will allow patients, their designates (e.g., substitute decision maker) and delegates to access information from DHDR via consumer applications using the Ontario Digital Health Drug Repository HL7 FHIR Patient Access Implementation Guide published by Ontario Health.

Model

The DHDR FHIR Consumer Query provides a backend interface to consumer applications to enable consumers (patients, their designates and delegates) to access the patient’s drug and pharmacy service information in the DHDR.

The DHDR solution includes:

Data repository of drug and pharmacy service information submitted to the DHDR
Validation of patient (client) information using provincial registries
APIs that allow consumer applications to query and display administered drug, dispensed drug, and pharmacy service information to patients
Integration with the Consumer ONE Access Gateway (OAG) for DHDR queries from patient consumer OAG for patient consumer applications

This data out query to the DHDR API occurs via the ONE Access Consumer Gateway to interact with Ontario’s Digital Health Drug Repository and Web Services (DHDR) solution.

The Consumer Application manages rules around access for a designated and delegated user to view DHDR data on behalf of a consumer. This includes but i not limited to rules around authenticating a user prior to submitting the query.

The diagram below illustrates the Business Context for DHDR Consumer Query implementation:

Business Model

Query Functionality

In order to comply with auditing and privacy requirements, the Consumer Application should provide the following information with every request

Name of the Consumer Application used to access DHDR
Name of the Consumer Application provider
Consumer Application Version
User Id
User Full Name (First Name and Last Name)
Type of User (Patient, Designate, Delegate)
Name of the health information custodian who first authorized the Individual User or Designated or Delegated User’s access