Ontario Subscription HL7® FHIR® Implementation Guide -v1.0.0-ballot1
For a full list of available versions, see the Directory of published versions
The Ontario Health Enterprise Publish and Subscribe Service is a foundational asset enabling real-time, event-driven data exchange across OH digital health assets. Designed to support FHIR-based subscription architecture, it allows healthcare systems to subscribe to specific clinical and administrative events, ensuring timely notifications and seamless information flow.
Key Capabilities:
The following diagram illustrates the Ontario Health Pub-Sub conceptual architecture, serving as the foundation for implementing system components, interactions, interoperability profiles, and underlying clinical terminology.
| Component | Description |
|---|---|
| Event Publisher | The system that publishes event notifications when relevant data change triggers an event |
| Topic | Specific type of healthcare event that subscribers can register for to receive real-time notifications. It acts as a predefined category of events, ensuring consistency and standardization in how notifications are triggered and delivered across the healthcare ecosystem. |
| Event Processor | Determines if a notification should be sent to a client based on the topics that listen to the resources in the notification data. If the data received from the publisher satisfies the topic resource trigger tests component will invoke the subscription notification processor for each subscription subscribed to the topic. |
| Notification Processor | The component used to filter event and notify subscribers when an event occurs. It is also responsible to submit heart beat notification event according to heart beat period paramter configuration. |
| Subscription Manager | Allow clients to receive notification events from an individual topic. Clients can create, get, update, and delete their subscriptions to any topic. Subscriptions Manager can filter notification events from an individual topic. Clients can receive a history of past notifications using the $events operation, and can also query the status of their subscription using $status. Clients cannot modify other subscriptions they did not create since an authentication token is used to validate requests. |
| List Manager | The component that allows subscribing systems to manage the lists of Patients and Practitioners associated with Subscriber (e.g., EMR instance) |
| Event Subscriber | The system that receives and processes notifications from the Subscription Manager. It also creates and manages subscriptions and lists. |
| Event Repository | The structured data store that manages and tracks FHIR Subscription resources. |