Home > Scope

Scope

This implementation guide is developed as part of Ontario Health's plan to facilitate the exchange of CorHealth data. Ontario CorHealth Registry is designed to enable collections and use of detailed data of cardiac procedures for patients who are ≥18 years of age who receive cardiac services in Ontario.

CorHealth Data Collection & Information System (DCIS) collects a variety of information for specific cardiac services performed in Ontario.

  • This data is used in the Ontario healthcare system to advance the quality, efficiency, accessibility, and equity of cardiac services for patients across Ontario by:
  • Driving evidence informed practice
  • Informing planning, access, and resource allocation
  • Measuring and reporting on quality and outcomes

The purpose of this implementation guide is to develop guidance and explore potential of using FHIR standard for CorHealth DCIS data submission and consumpton. This aligns with the provincial DHIEX regulation 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 FHIR representation of CorHealth DCIS data.

Applying the CorHealth HL7 FHIR IG

TBD: Ontario Health will be establishing the CorHealth HL7 FHIR IG 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.
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.) To be determined
Name, description, or class of Health Information Custodians that must select, develop, or use digital health assets that comply with the specification: To be determined
Types of digital health assets to which the specification applies: To be determined
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: To be determined