Ontario Health
Ontario Clinical Report Exchange Implementation Guide v1.0.0 - Trial Use
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
    • Profiles
    • Extensions
    • Terminology
    • System URIs
    • Examples
    • Capability Statement
    • 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

This implementation guide is developed as part of Ontario Health's plan to facilitate the submission of OCRE data by data contributors. This IG will also be used by point of service systems (e.g. EMRs, etc) who will subscribe to OH Pub/Sub services to receive OCRE reports.

The purpose of this implementation guide is to develop guidance for using FHIR R4 standard for OCRE data submission and consumpton. This aligns with the provincial DHIEX program which stipulates that FHIR will be the primary healthcare interoperability standard in health data exchange in Ontario.

The current design of this implementation guide focuses on alignment of OCRE data with Ontario EHR profiles and with Ontario acCDR and MI FHIR IGs.

1.3.1. Applying OCRE FHIR IG

Ontario Health will be establishing the OCRE 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.) N/A - Balloted Draft
Name, description, or class of Health Information Custodians that must select, develop, or use digital health assets that comply with the specification: For OCRE data contribution:
  • Hospitals within the meaning of the Public Hospitals Act.
  • Integrated Community Health Services Centres (ICHSC) within the meaning of the Integrated Community Health Services Centres Act, 2023
For OCRE data consumption:
  • Healthcare providers that subscribe to OCRE reports for patient care (e.g. primary care clinics)
Types of digital health assets to which the specification applies For OCRE data contribution:
  • Hospital Information Systems and/or ancillary systems utilized by Hospitals within the meaning of the Public Hospitals Act. Information systems utilized by ICHSCs.
For OCRE data consumption:
  • EMR systems that receive reports from OCRE. Other point of service systems that need to comply with this specification will be determined in the future to support additional use cases.

    "An electronic medical record (EMR) generally refers to an electronic version of the paper health record. An EMR system can be used by one or more health information custodians in a primary care practice setting or community-based care setting to collect or use personal health information such as a patient's family history, lab requests and results, cancer screening tests, emergency room visits, prescriptions, etc, for the provision of care."
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 using the combined feed v2.6.1 and above to acCDR and OCRE can continue to use the acCDR Input Specification and are not required to comply with this specification.
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