Table of Contents > Business Model
Context
The overall objective of the Surgical Efficiency Reporting Information System (SERIS) is to capture OR Case information as well as OR Schedules in near-real-time to facilitate multi-stakeholder decision making.
The product will leverage a standardized specification defining the electronic data interchange based on HL7-FHIR. The new developed standard will be accompanied by an Implementation Guide (IG) defining an API usable by participating hospitals.
SERIS is expected to commence collecting PHI in FY23-24. This will increase the visibility of the surgical patient’s journey when linked to WTIS and eReferral data. Collected data will be used to detect and highlight bottlenecks due to a lack of resources to address demand, growing waitlists, cancellations, and inefficiency. It will facilitate informed decision making and supports the identification of solutions to improve surgical capacity and OR availability.
SERIS Patient Flow
Conceptual Solution
The modernized SERIS Product is a recipient system that requires Facilities to contribute OR Case and Operating Room (OR) data in near real-time. The collection of SERIS data will be based on the Fast Healthcare Interoperability Resources (FHIR) standard supported by an HTTP API. SERIS will be integrated with the facility system to varying degrees depending upon each facility to meet the SERIS requirements.
| Component | Definition |
|---|---|
| SERIS API | RESTful HTTP based API. |
| Web Client | Future state web application for support and alternate use case submissions. |
| Data Sets | OR Case & OR Schedule. |
| Payload | Various FHIR R4 resources depending on dataset. |
| Authentication | Ontario Health ONE ID. |
| Gateway | Secure gateway for transmission of FHIR payloads. |
| System Consumers | Various consumers and stakeholders such as the Ministry of Health, Ontario Health and contributing facilities. |
High Level Requirements
| Req # | High Level Requirement |
|---|---|
| 1 | Ability for facilities to submit an OR Schedule. |
| 2 | Ability for facilities to submit updates to OR Schedule. |
| 3 | Ability for facilities to submit OR Cases. |
| 4 | Ability for facilities to submit updates to OR Cases. |
| 5 | Ability for facilities to submit OR Case Cancelations. |
| 6 | Ability for facilities to correct data entered in error. |
Systems
OR Administration is an electronic product, service or system that uses electronic means to manage the daily activities of an individual or group of Surgical Operating Suites within a healthcare site. Examples include but are not limited to: a hospital information system (HIS).
The SERIS Repository is an Ontario Health digital health asset that supports the capture of OR Case information as well as OR Schedules in near-real-time to faciliate multi-stakeholder decision making.