Home > Introduction

Introduction

Overview

The Digital Health Drug Repository (DHDR) is a provincial source of drug and pharmacy service information that improves the quality of care received by people living in Ontario by making comprehensive dispensed drug and pharmacy service information available for access by health care providers.

The DHDR is being expanded to include information from community pharmacies and hospital pharmacies in addition to information currently contributed from the Ministry of Health.

COVID-19 vaccination information from COVaxON (the ministry’s provincial solution for COVID-19 vaccination information) is also available through the DHDR. COVaxON includes information on all COVID-19 vaccinations administered by any health care provider in any location in the province.

This FHIR implementation guide supports:

  • Contribution to the DHDR of dispensed drug and pharmacy services records from community Pharmacy Management Systems

  • Contribution to the DHDR of administered drug records from Hospital Information Systems

  • Retrieval of DHDR records by health care provider applications via the ONE Access gateway

Digital Health Information Exchange (DHIEX)

On January 1, 2021, the regulation to the Personal Health Information Protection Act, 2004 (PHIPA), O. Reg. 329/04 (“the regulation”), was amended to provide a regulatory framework (Digital Health Information Exchange (DHIEX) framework) for Ontario Health, as directed by the Minister of Health, to establish, maintain and amend interoperability specifications, as set out in sections 26 to 34 of the regulation. Ontario Health refers to its authorities under the regulation (specifically sections 26 to 34) as the Digital Health Information Exchange (DHIEX).

Ontario Health guides and supports the adoption of modern interoperability specifications for seamless access to integrated records of personal health information. In accordance with O. Reg. 329/04, the interoperability specifications are applicable to digital health assets selected, developed or used by health information custodians. In addition, a health information custodian is required to ensure that every digital health asset that it selects, develops or uses complies with every applicable interoperability specification, as it may be amended from time to time, within the time period set out in the specification.

Compliance with this requirement does not relieve a health information custodian of its obligation to comply with the other provisions of PHIPA and its regulations.

The following will also be included in the glossary of each spec and at the first instance of the term "DHIEX framework" in each spec "Ontario Health refers to its authorities under the regulation (specifically sections 26 to 34) as the Digital Health Information Exchange (DHIEX).

Ontario Health is required to consult with and consider the recommendations of the Information and Privacy Commissioner (where a specification relates to the confidentiality of personal health information, the privacy of individuals or the rights of individuals to access or correct records of their personal health information) prior to providing the specification to the Minister of Health for review and approval.

Content and Organization

The implementation guide is organized into the following sections:

This specification is fully copyright protected by the owner. The owner has the exclusive right to make copies of this specification. No alterations, deletions or substitutions may be made without the prior written consent of the owner. No part of it may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopy, email or any information storage and retrieval system, without the prior written consent of the owner.

This specification contains information for which copyright is held by Health Level Seven, Inc. There is no membership requirement for individuals and organizations which merely install or use software with built-in HL7 interfaces.

HL7® and FHIR® are registered trademarks of Health Level Seven, Inc. (https://www.hl7.org).

LOINC® is a registered trademark of the Regenstrief Institute, Inc. (http://regenstrief.org)

This material includes SNOMED Clinical Terms® (SNOMED CT®) (https://www.snomed.org/snomed-ct/) which is used by permission SNOMED International. All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists.

“SNOMED” and “SNOMED CT” are registered trademarks of SNOMED International (https://www.snomed.org/).

Disclaimer

Pursuant to O. Reg. 329/04, Ontario Health is required to, subject to the review and approval of the Minister, establish, maintain and amend interoperability specifications. The Minister may direct Ontario Health to establish or amend interoperability specifications, and Ontario Health is required to comply with such direction.

In accordance with O. Reg. 329/04, Ontario Health makes the interoperability specification most recently approved by the Minister available to the public by posting it on Ontario Health’s website or by such other means as Ontario Health considers advisable.

As the Minister may direct Ontario Health to amend the interoperability specifications from time-to-time, Ontario Health advises the public and any other users of information concerning interoperability specifications to regularly review Ontario Health’s website where the interoperability specifications are posted, or such other means Ontario Health considers advisable, in order to confirm that they are accessing the interoperability specifications most recently approved by the Minister.

You understand and agree that:

(i) This specification is provided “AS IS” without any warranties or representations of any kind, express or implied, in fact or in law;

(ii) Ontario Health is not responsible for your use or reliance on the information in this specification or any costs associated with such use or reliance; and

(iii) Ontario Health has no liability to any party for that party’s access, use or reliance on this specification or any of the information contained in it.

Document Control

The electronic version of this specification is recognized as the only valid version.

Approval History

APPROVER(S) APPROVED DATE
YYYY-MM-DD