visit the hl7 website
Ontario IG Template
fhir-logo
  • Index
  • Home
    • Home
    • Introduction
    • Relationship to Other Specifications
    • Scope
    • Glossary
  • Business Context
    • Business Context
    • Business Model
    • Business Data
    • Use Cases
    • Business Rules
  • Technical Context
    • Technical Context
    • Implementer Responsibility
    • Conformance Rules
    • Connectivity Summary
  • FHIR Artifacts
    • FHIR Artifacts
    • Interactions
    • Operations
    • Profiles
    • Extensions
    • Data Types
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • Custom Search Parameters
    • Response Handling
    • Downloads
  • Change Log
    • Change Log
    • Known Issues & Future Developments
    • Revision History
    1. Index
    2. Home
    3. Scope

For a full list of available versions, see the Directory of published versions

1.3. Scope

Important Note to IG Authors:
This is a template only. All sample text, examples, and placeholders must be replaced with the specific project scope information, and include figures/diagrams if relevant.
If the IG is not being established under DHIEX, remove or adapt the DHIEX framing text.

[Insert project Scope here along with any figures or diagrams that are relevant]


1.3.1. Applying [IG Name] FHIR IG

Ontario Health will be establishing the [IG Name] as an interoperability specification under Ontario’s Digital Health Information Exchange (DHIEX) framework.

The following information is provided in accordance with O. Reg. 329/04 under Personal Health Information Protection Act (PHIPA), 2004, section 28 Application of Specifications.

Contribution from community pharmacies is voluntary; however, should they choose to contribute, then compliance with the interoperability specification is mandatory.

Requirement Details
Date on which the specification becomes effective (Note:  This is the date by which all applicable HICs are required to be compliantly contributing and/or consuming the approved interoperability specification. OH will work with the applicable HICs to establish the implementation plan in order to meet the effective date.) TBD
Name, description, or class of Health Information Custodians that must select, develop, or use digital health assets that comply with the specification: Health Information Custodians who contribute data to [IG Name]:
- Hospitals as per the Public Hospitals Act, R.R.O. 1990, Reg. 965.
- Community pharmacies as per the Drug and Pharmacies Regulation Act, O. Reg. 264/16.

Health Information Custodians who view [IG Name] data:
- All HICs as per Section 3 of PHIPA compliant and authorized per Ontario Health agreements to access or integrate with the EHR
Types of digital health assets to which the specification applies Digital health assets used by Health Information Custodians for the above purpose:
- Hospitals using a Health Information System (HIS) which has modules to support medication administration management and pharmacy management
- Authorized HICs using applications and systems which query the [IG Name] such as provincial viewers, electronic medical record systems and HISs
Circumstances, if any, when a Health Information Custodian may be exempted from the requirement to select, develop or use digital health assets that comply with the specification: - Hospitals within the meaning of the Public Hospitals Act , R.R.O. 1990, Reg. 965 contributing or planning to contribute medication administration data using the acCDR Input Standard v2.6
- In-patient pharmacies within hospitals are exempted from contribution of medication dispense data
- Community pharmacies are exempted from mandatory contribution of medication dispense data
Version: 1.0.0 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

HL7® and FHIR® are the registered trademarks of Health Level Seven International