Ontario Immunization Repository Implementation Guide -v1.0.0-draft2
For a full list of available versions, see the Directory of published versions
The following rules govern how data is accepted, validated, and persisted within the Immunization Repository.
| Req ID | Requirement Description |
|---|---|
| IR-BR-001 | All submissions shall include mandatory Patient attributes (Patient ID, Name, Date of Birth, and Gender). Contributions missing these elements will not be persisted. |
| IR-BR-007 | The system shall treat a record as a duplicate and reject it if it matches an existing IR record based on a combination of: Patient ID, UAO, Immunization Record ID, Agent, and Date Administered. |
| IR-BR-008 | Every immunization record must include a unique, stable business key (UAO + Immunization Record ID) to support deterministic processing of updates and logical deletes. |
| IR-BR-009 | Data governance rules restrict updates to the original contributing Health Information Custodian (HIC); the system shall reject update requests originating from a different HIC. |
| IR-BR-011 | Validation of display name for Panorama shall account for shortened French/English display names (tailored to Panorama's field length limitation). |
These rules define the logic for synchronizing data from the Immunization Repository to downstream systems like Panorama.
| Req ID | Requirement Description |
|---|---|
| IR-DO-006 | The system shall transmit immunization record corrections and logical delete events to Panorama whenever a record is modified within the IR. |
| IR-DO-007 | Data-out transmissions must include an incremental version identifier with each record to indicate the relative recency of the information. |
| IR-DO-008 | The system shall use a unique business key (System ID + Immunization Record ID) to match and identify records across all synchronization events. |
| IR-DO-011 | Immunization records shall continue to be transmitted for synchronization purposes between systems even when a client-level consent block is in place. |