visit the hl7 website
Ontario Immunization Repository Implementation Guide -v1.0.0-draft2
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
    • 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

In Scope

This Implementation Guide provides the FHIR conformance (profiles, transactions, and terminology) for the following:

  • Contributing Actors:

    • Panorama: For ongoing data contributions and bi-directional synchronization from Public Health Units.
    • Community Pharmacy Management Systems (PMS): For direct, real-time submission of immunization records administered at community pharmacies.
  • Querying Actors

    • Panorama
    • Community Pharmacy Management Systems (PMS)
    • Provincial Viewers
    • Electronic Medical Record Systems
    • Health Information Systems

  • Data Transactions

    • Data In:

      • Submission: The creation of new immunization and client records in the IR.
      • Corrections & Updates: The ability for the original source system to submit updates or correct clerical errors.
      • Invalidation: The ability for the original source system to logically delete or mark a record as "Entered-in-Error".
    • Data Out:

      • Synchronization: Transmission of immunization records, updates, and logical deletes from the IR back to Panorama.
      • Any transactions to query or read data from the IR such as provincial viewers, electronic medical record systems and HISs.

  • Core Infrastructure Integration:

    • Standards for identity resolution through the Provincial Client Registry (PCR) and provider validation through the Provincial Provider Registry (PPR).
    • Enforcement of consent directives through the Consent Management Technology Asset (CMTA).

Out of Scope This Implementation Guide does not define standards or transactions for the following:

  • Bulk Historical Loads: The one-time bulk load of historical data from Panorama or other sources is defined separately.
  • Other Data Sources: Contributions from Primary Care, Hospitals, Long-Term Care Homes (LTCH), or Indigenous health systems (planned for future work packages).
  • External Requests: Direct ongoing data retrieval requests from PMS, HIS, or EMR systems.
  • User Interfaces: The design of "Quick-entry" forms or specific clinical/patient viewers.
  • Consent Management: The administrative processes for creating, updating, or removing consent directives (managed by the Ontario Health Privacy Office).

1.3.1. Applying Ontario Immunization Repository FHIR IG

Ontario Health will be establishing the Ontario Immunization Repository 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.

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 IR:
- 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.
- Public Health Units (PHUs) as per the Health Protection and Promotion Act, R.S.O. 1990 (Ontario Public Health Standards under s.7); Immunization of School Pupils Act, R.S.O. 1990, c. I.1 and O/Reg. 645, through the Panorama solution
- MOH in respect of COVID-19 vaccination data collected under the COVID-19 Vaccination Reporting Act, 2021, S.O. 2021, c. 27

Health Information Custodians who view IR data:
- All HICs as per Section 3 of PHIPA 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:
- Health Information System (HIS) which has modules to record vaccine administration management
- Pharmacy management systems used by community pharmacies
- Panorama system used by Public Health Units (PHU)
- Applications and systems which query the IR 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: Public Health Units (PHU) in respect of current local EMR systems used to contribute data to Panorama
Version: 1.0.0-draft2 FHIR Version: R4.0.1

Powered by SIMPLIFIER.NET

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