Home > Scope
This document serves as a technical specification for implementing HL7 Fast Healthcare Interoperability Resources (FHIR) messages in order to interact with Ontario’s Provincial Consent Override Interface service. Sufficient business rationale is provided to illustrate the scenarios that the specification aims to fulfill. Storyboards, interactions, message types, vocabulary, data types, object identifiers, and FHIR message examples are included to facilitate the implementation process.
This document provides functional implementation guidance for the HL7 FHIR operations defined to submit consent override requests to the Ontario Health PCOI service.
For PCOI Release 1, only the Digital Health Drug Repository is in scope.
General PCOI and PCOI Viewlet onboarding guidance including delivery methodology, required resources, and conformance testing requirements are currently out-of-scope for this document. Please contact the Ontario Health inset product or onboarding team here at **iap@ehealthontario.on.ca** to initiate an integration with PCOI or the PCOI Viewlet and receive supporting onboarding material.
PCOI FHIR implementation guidance pertaining to non-functional connectivity with the Ontario Health Provider Gateway, including ONE ID and OAuth2 requirements, is currently out-of-scope for this document. Please refer to the cross-reference links defined under the “Connectivity Summary” sub-section accordingly.
The process to create Patient Privacy Consent Blocks is beyond the scope of the document. Please contact the respective Ontario Health Line of Business for detailed process to create Patient Privacy Consent Blocks.
Ontario Health will be establishing the Ontario Provincial Consent Override Interface HL7 FHIR IG as an interoperability specification under Ontario’s Digital Health Information Exchange (DHIEX) framework.
The following information is provided in accordance with section 28 of O. Reg. 329/04 made under the Personal Health Information Protection Act (PHIPA), 2004.
| Date on which the specification becomes effective: |
|
|---|---|
| Name, description, or class of Health Information Custodians that must select, develop, or use digital health assets that comply with the specification: |
|
| Types of digital health assets to which the specification applies: |
|
| 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: |
|
Powered by SIMPLIFIER.NET